public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Jean Delvare <khali@linux-fr.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Amit Kucheria <amit.kucheria@verdurent.com>
Subject: Re: [PATCH] isl29003: Move from misc to als now it available with minimal changes
Date: Thu, 11 Feb 2010 19:34:17 +0100	[thread overview]
Message-ID: <20100211183417.GS9007@buzzloop.caiaq.de> (raw)
In-Reply-To: <4B23DA53.9090008@cam.ac.uk>

Hi Jonathan,

On Sat, Dec 12, 2009 at 06:00:51PM +0000, Jonathan Cameron wrote:
>  I originally offered to move this to IIO, but ALS is more appropriate.
>  There are a couple of attibutes in here that don't correspond directly
>  to any currently in ALS. Feel free to offer suggestions for renames etc
>  on these, but I'd prefer to see them in a second patch allowing us to
>  keep things in this movement patch nice and clean. Will do api help
>  once these are pinned down.

Thanks again for doing this. I gave that ported driver a quick test and
it seems to work fine. Just one thing below ...

> diff --git a/drivers/misc/isl29003.c b/drivers/als/isl29003.c
> similarity index 90%
> rename from drivers/misc/isl29003.c
> rename to drivers/als/isl29003.c
> index a71e245..2ab188e 100644
> --- a/drivers/misc/isl29003.c
> +++ b/drivers/als/isl29003.c
> @@ -31,9 +31,10 @@
>  #include <linux/i2c.h>
>  #include <linux/mutex.h>
>  #include <linux/delay.h>
> +#include <linux/als_sys.h>

You need linux/err.h here. Without that, it breaks at compile time on a
PXA board as 'PTR_ERR' and 'IS_ERR' are undefined.

Apart from that:

Acked-by: Daniel Mack <daniel@caiaq.de>


      reply	other threads:[~2010-02-11 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-12 18:00 [PATCH] isl29003: Move from misc to als now it available with minimal changes Jonathan Cameron
2010-02-11 18:34 ` Daniel Mack [this message]

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=20100211183417.GS9007@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=amit.kucheria@verdurent.com \
    --cc=jic23@cam.ac.uk \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.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