From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Greg KH <greg@kroah.com>, Greg Kroah-Hartman <gregkh@suse.de>,
devel@driverdev.osuosl.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH 3/3] staging:iio: Fix scan mask update
Date: Sun, 18 Dec 2011 20:44:06 +0100 [thread overview]
Message-ID: <4EEE4286.5040101@metafoo.de> (raw)
In-Reply-To: <4EEE2A9F.4080602@kernel.org>
On 12/18/2011 07:02 PM, Jonathan Cameron wrote:
> On 12/09/2011 03:11 PM, Greg KH wrote:
>> On Fri, Dec 09, 2011 at 10:49:45AM +0100, Lars-Peter Clausen wrote:
>>> On 12/08/2011 09:18 PM, Greg KH wrote:
>>>> On Thu, Dec 08, 2011 at 06:35:53PM +0100, Lars-Peter Clausen wrote=
:
>>>>> When updating the scan mask we have to check the actual scan mask=
for if the
>>>>> channel is already enabled, not the matching scan mask from the a=
vailable
>>>>> scan masks. The bit will already be set there and as a result the=
actual
>>>>> scan mask will not get updated and the channel stays disabled.
>>>>>
>>>>> Also fix the return value of iio_scan_el_store which would return=
1 instead of
>>>>> the number of bytes written if the channel was already active in =
the scan mask.
>>>>
>>>> You just added a complier warning with this patch:
>>>> CC [M] drivers/staging/iio/industrialio-buffer.o
>>>> drivers/staging/iio/industrialio-buffer.c: In function =E2=80=98ii=
o_scan_mask_query=E2=80=99:
>>>> drivers/staging/iio/industrialio-buffer.c:621:8: warning: unused v=
ariable =E2=80=98mask=E2=80=99 [-Wunused-variable]
>>>>
>>>> So I didn't apply it.
>>>
>>> Actually you did. At least it is in staging-next. Should I resend a=
updated
>>> patch or just a patch removing the now unused mask variable.
>>
>> Ugh, you are right, I was messing with my scripts to apply patches a=
t
>> the time, and forgot to delete this branch.
>>
>> So, please send a follow-on patch to fix the warning.
>>
> Lars-Peter, have you sent such a patch to Greg? I'm still seeing thi=
s
> warning hence the bump! Just wondering if this got lost in amongst
> everything else that is going on.
Haven't send it out yet. Will do tomorrow.
prev parent reply other threads:[~2011-12-18 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 17:35 [PATCH 1/3] staging:iio: Fix sw_ring memory corruption Lars-Peter Clausen
2011-12-08 17:35 ` [PATCH 2/3] staging:iio:kfifo_buf: Fix potential buffer overflow in iio_read_first_n_kfifo Lars-Peter Clausen
[not found] ` <20111208201722.GA31926@kroah.com>
2011-12-09 9:58 ` Lars-Peter Clausen
2011-12-09 15:11 ` Greg KH
2011-12-08 17:35 ` [PATCH 3/3] staging:iio: Fix scan mask update Lars-Peter Clausen
2011-12-08 20:18 ` Greg KH
2011-12-09 9:49 ` Lars-Peter Clausen
2011-12-09 15:11 ` Greg KH
2011-12-18 18:02 ` Jonathan Cameron
2011-12-18 19:44 ` Lars-Peter Clausen [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=4EEE4286.5040101@metafoo.de \
--to=lars@metafoo.de \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jic23@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).