All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>,
	"lars@metafoo.de" <lars@metafoo.de>
Subject: Re: [PATCH] staging:iio:isl29028 Add IIO_CHAN_INFO_RAW/PROCESSED entries
Date: Sun, 15 Apr 2012 21:01:18 +0530	[thread overview]
Message-ID: <4F8AE9C6.9010901@nvidia.com> (raw)
In-Reply-To: <4F8AD058.6030705@kernel.org>

On Sunday 15 April 2012 07:12 PM, Jonathan Cameron wrote:
> On 04/15/2012 12:41 PM, Jonathan Cameron wrote:
>> Precursor to making value read / write attribute optional.
>> This one stands along as it merged just before the series
>> doing all the other drivers.
>>
> Note there is also a one line change to remove the processed_val line
> in the obvious patch later in the series...
>
>> Signed-off-by: Jonathan Cameron<jic23@kernel.org>
>>

Acked-by: Laxman Dewangan <ldewangan@nvidia.com>

changes make more sense now.  I was thinking that what is mask 0 when I 
started this driver and after reading  other driver came to know about this.
>>   		switch (chan->type) {
>>   		case IIO_LIGHT:
>>   			ret = isl29028_als_get(chip, val);
>> @@ -391,12 +392,15 @@ static const struct iio_chan_spec isl29028_channels[] = {
>>   	{
>>   		.type = IIO_LIGHT,
>>   		.processed_val = 1,

processed_val should be removed here and already you have taken care.


-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------

  reply	other threads:[~2012-04-15 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 11:41 [PATCH] staging:iio:isl29028 Add IIO_CHAN_INFO_RAW/PROCESSED entries Jonathan Cameron
2012-04-15 13:42 ` Jonathan Cameron
2012-04-15 15:31   ` Laxman Dewangan [this message]
2012-04-15 16:29     ` Jonathan Cameron

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=4F8AE9C6.9010901@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.