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>
Subject: Re: [PATCH 0/6] iio:trivial dev_info rename + remove unneeded existence checks
Date: Thu, 06 Oct 2011 17:18:23 +0100 [thread overview]
Message-ID: <4E8DD4CF.1080204@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D59177146E73435AB@LIMKCMBX1.ad.analog.com>
On 10/05/11 07:37, Hennerich, Michael wrote:
> Jonathan Cameron wrote on 2011-10-03:
>> Hi All,
>>
>> The trigger patches should be trivial and obvious.
>>
>> The dev_info / indio_dev was entirely my fault as I introduced both
>> names a long time ago. For a while drivers were at least internally
>> consistent, but with all the recent tree wide changes this is no
>> where near true. Hence I did a word count, established dev_info
>> is no where near as common and hence have replaced all instances
>> in IIO with indio_dev (except for a few drivers for various reasons).
>>
>> Should have done this a long time ago. Sorry for the churn of the
>> tree that will result.
>>
>> Note this is on top of all patches I have currently published.
>
> Looks good.
> As far as the ADxxxx are concerned.
>
> Acked-by: Michael Hennerich <michael.hennerich@analog.com>
I've done a bit of naughty history editing and broken this
set in two. The rename patches have no gone to Greg. I'll
roll the other two into a later series.
(this is mostly because I got it into my head that I hadn't
posted the trigger ones yet and hence along with some other
patches shunted them forwards in time - one day I'll be good
and use topic branches rather than my stream of conciousness
and editing approach to patches).
Anyhow, they are now in the github master branch which I'm
keeping at the point of whatever I have sent Greg.
Jonathan
prev parent reply other threads:[~2011-10-06 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 15:08 [PATCH 0/6] iio:trivial dev_info rename + remove unneeded existence checks Jonathan Cameron
2011-10-03 15:08 ` [PATCH 1/6] staging:iio:triggers Remove unecessary existence checks and return val Jonathan Cameron
2011-10-03 15:08 ` [PATCH 2/6] staging:iio:industrialio-trigger.c Trivial code style brackets fix Jonathan Cameron
2011-10-03 15:08 ` [PATCH 3/6] staging:iio:core:naming: dev_info to indio_dev for consistency Jonathan Cameron
2011-10-03 15:08 ` [PATCH 4/6] staging:iio:accel:sca3000 dev_info to indio_dev renaming Jonathan Cameron
2011-10-03 15:08 ` [PATCH 5/6] staging:iio:adc:naming: dev_info to indio_dev for consistency Jonathan Cameron
2011-10-03 15:08 ` [PATCH 6/6] staging:iio:dac/dds/impedance " Jonathan Cameron
2011-10-05 6:37 ` [PATCH 0/6] iio:trivial dev_info rename + remove unneeded existence checks Hennerich, Michael
2011-10-06 16:18 ` Jonathan Cameron [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=4E8DD4CF.1080204@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--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).