From: Michael Hennerich <michael.hennerich@analog.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>
Subject: Re: [PATCH 3/3] iio: amplifiers: New driver for AD8366 Dual-Digital Variable Gain Amplifier
Date: Fri, 11 May 2012 09:32:10 +0200 [thread overview]
Message-ID: <4FACC07A.8080600@analog.com> (raw)
In-Reply-To: <4FAB859F.2060103@kernel.org>
On 05/10/2012 11:08 AM, Jonathan Cameron wrote:
> On 5/9/2012 11:36 AM, michael.hennerich@analog.com wrote:
>> From: Michael Hennerich<michael.hennerich@analog.com>
>>
>> Changes since V1:
>>
>> Apply review feedback:
>> Introduce and use IIO_CHAN_INFO_HARDWAREGAIN
>> Introduce and use Use IIO_VAL_INT_PLUS_MICRO_DB
>>
>> Modify out of staging include paths.
>> Convert to new iio core API naming.
> For reasons I don't understand thunderbird on windows (yes I'm doing
> this whilst waiting for something to run at the day job), is wrecking
> spacing in subtle ways despite being in plain text mode... Grr.
>
> Anyhow, my only real comment is that I think we may want a little more
> value sanity checking in the write_raw function. Not critical as
> hopefully no one will write anything stupid to that, but nice to lock
> down anyway if you have the time.
Hi Jonathan,
Will add a check for val < 0 || val2 < 0.
If you don't mind I'll target the patch to the out of staging iio folder.
drivers/iio/amplifiers/ad8366.c
>> Signed-off-by: Michael Hennerich<michael.hennerich@analog.com>
> Acked-by: Jonathan Cameron<jic23@kernel.org>
>
--
Greetings,
Michael
--
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin,
Margaret Seif
next prev parent reply other threads:[~2012-05-11 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 10:36 [PATCH 1/3] iio: core: introduce dB scle: IIO_VAL_INT_PLUS_MICRO_DB michael.hennerich
2012-05-09 10:36 ` [PATCH 2/3] iio: core: introduce IIO_CHAN_INFO_HARDWAREGAIN michael.hennerich
2012-05-10 8:09 ` Jonathan Cameron
2012-05-09 10:36 ` [PATCH 3/3] iio: amplifiers: New driver for AD8366 Dual-Digital Variable Gain Amplifier michael.hennerich
2012-05-10 9:08 ` Jonathan Cameron
2012-05-11 7:32 ` Michael Hennerich [this message]
2012-05-11 7:36 ` Jonathan Cameron
2012-05-10 8:09 ` [PATCH 1/3] iio: core: introduce dB scle: IIO_VAL_INT_PLUS_MICRO_DB Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2012-05-11 9:36 michael.hennerich
2012-05-11 9:36 ` [PATCH 3/3] iio: amplifiers: New driver for AD8366 Dual-Digital Variable Gain Amplifier michael.hennerich
2012-05-14 20:13 ` Greg KH
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=4FACC07A.8080600@analog.com \
--to=michael.hennerich@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--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).