From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
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 0/2] IIO more resolver cleanups.
Date: Mon, 23 May 2011 16:35:46 +0100 [thread overview]
Message-ID: <4DDA7ED2.5020807@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D5917713AAF293900@LIMKCMBX1.ad.analog.com>
On 05/23/11 15:52, Hennerich, Michael wrote:
> Jonathan Cameron wrote on 2011-05-20:
>> What can I say, this morning has turned out to be rather dull as well
>> and these other two drivers are small so here is a cleanup series for
>> them.
>>
>> Note in the ad2s1210 driver I forgot to clear the IN / OUT of
>> resolution bit out of the Kconfig file. I'm also not entirely sure I
>> understand how that is supposed to work, so may well have it wrong.
>>
>> Thanks,
>
> Hi Jonathan,
>
> Thanks for having dull times.
> Really nice cleanup!
>
> Give me some time to review these - unfortunately I don't have hardware to
> test at the moment.
>
Sure. This is in the next big round anyway as I don't really want to push
anything else in this merge window. Feel I've been mean enough to Greg
already!
Jonathan
next prev parent reply other threads:[~2011-05-23 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 9:41 [RFC resolvers] How to handle fault conditions Jonathan Cameron
2011-05-20 9:41 ` [PATCH] staging:iio:resolver:ad2s1210 general driver cleanup Jonathan Cameron
2011-05-20 10:58 ` [PATCH 0/2] IIO more resolver cleanups Jonathan Cameron
2011-05-23 14:52 ` Hennerich, Michael
2011-05-23 15:35 ` Jonathan Cameron [this message]
2011-05-20 10:58 ` [PATCH 1/2] staging:iio:resolver:ad2s120x cleanup Jonathan Cameron
2011-05-20 10:58 ` [PATCH 2/2] staging:iio:resolver:ad2s90 general cleanup 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=4DDA7ED2.5020807@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.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