From: Barry Song <21cnbao@gmail.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Matthias Brugger <mensch0815@gmail.com>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] Staging: adis16255: Fix compile error
Date: Tue, 4 May 2010 10:44:35 +0800 [thread overview]
Message-ID: <y2q3c17e3571005031944z321ffb98w54b5534dcf195ec6@mail.gmail.com> (raw)
In-Reply-To: <1272819933.16886.19.camel@lenovo>
The main work of this driver is providing sys node for users to access
data. Which directory will this driver be placed after moving from
staging? It's better to rewrite it based on IIO. Otherwise, the
architecture for this kind of driver will be difficult to be
consistent.
-barry
On Mon, May 3, 2010 at 1:05 AM, Javier Martinez Canillas
<martinez.javier@gmail.com> wrote:
>
> This patch solves a compilation error in today linux-next tree.
>
> The adis16255 staging driver Makefile seems to be wrong. I think this patch solves the issue.
>
> Signed-off-by: Javier Martinez Canillas <martinez.javier@gmail.com>
> ---
> drivers/staging/adis16255/Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/staging/adis16255/Makefile b/drivers/staging/adis16255/Makefile
> index 3f8b1f0..dc4debc 100644
> --- a/drivers/staging/adis16255/Makefile
> +++ b/drivers/staging/adis16255/Makefile
> @@ -1 +1 @@
> -obj-$(CONFIG_ADIS16255) +�is16255.o
> +obj-$(CONFIG_ADIS16255) += adis1625.o
> --
> 1.7.0.4
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2010-05-04 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 17:05 Javier Martinez Canillas
2010-05-04 2:44 ` Barry Song [this message]
2010-05-04 14:44 ` matthias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y2q3c17e3571005031944z321ffb98w54b5534dcf195ec6@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=mensch0815@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®