From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mike Frysinger <vapier@gentoo.org>
Cc: device-drivers-devel@blackfin.uclinux.org, linux-iio@vger.kernel.org
Subject: Re: [Device-drivers-devel] [PATCH 00/36] staging: iio: ADI drivers for staging-next
Date: Mon, 25 Oct 2010 00:41:54 +0100 [thread overview]
Message-ID: <4CC4C442.5000304@cam.ac.uk> (raw)
In-Reply-To: <AANLkTi=iuV0QuCKWROfbEiX9E9qEsTH=Bh1bjC0FBcv_@mail.gmail.com>
On 10/24/10 22:35, Mike Frysinger wrote:
> On Sun, Oct 24, 2010 at 17:22, Mike Frysinger wrote:
>> I've rebased all the drivers onto staging-next. I've only fixed the API
>> breakage due to the changes made after 2.6.36 (and fixed a few warnings).
>> I've also run checkpatch across these.
>>
>> I have not however addressed any real feedback Jonathan has provided with
>> regards to driver correctness or direction. That stuff I'm leaving up to
>> Michael Hennerich since it's his job and he actually understands this.
>>
>> Where possible, I'd like to have drivers merged so as to avoid another
>> round of "new API just broke all your drivers". We will still look into
>> feedback given, but we'd like to focus on that rather than random `sed`
>> changes as API names change.
>
> btw, how does the merging with IIO occur ? do you take care of
> bouncing them to gregkh ? or does he watch this list ? or do i have
> to cc him too ?
CC Greg, or if the set has been on list then send them to him directly
and just post on the list that they have gone to Greg.
>
> my assumption is that i send IIO patches to you and then you get them
> into the staging tree ...
Normally I just suggest people send them to Greg. That is definitely
the case with this set as I'm off on holiday tomorrow evening and
hence won't be able to respond to any queries that come up and might
block the merge.
Hence over to you. Perhaps hold off until everyone has gotten to their
email tomorrow just in case....
Jonathan
next prev parent reply other threads:[~2010-10-24 23:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 21:22 [PATCH 00/36] staging: iio: ADI drivers for staging-next Mike Frysinger
2010-10-24 21:22 ` [PATCH 01/36] staging: iio: new adis16201 driver Mike Frysinger
2010-10-24 21:22 ` [PATCH 02/36] staging: iio: new adis16203 driver Mike Frysinger
2010-10-24 21:22 ` [PATCH 03/36] staging: iio: new adis16204 driver Mike Frysinger
2010-10-24 21:22 ` [PATCH 04/36] staging: iio: new ADT7316/7/8 and ADT7516/7/9 driver Mike Frysinger
2010-10-24 21:22 ` [PATCH 05/36] staging: iio: adc: new driver for AD7150/1/6 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 06/36] staging: iio: adc: new driver for AD7152/3 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 07/36] staging: iio: adc: new driver for AD7291 devices Mike Frysinger
2010-10-25 13:41 ` BUILD ISSUE: " Jonathan Cameron
2010-10-25 13:40 ` Hennerich, Michael
2010-10-25 14:00 ` Jonathan Cameron
2010-10-24 21:22 ` [PATCH 08/36] staging: iio: adc: new driver for AD7298 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 09/36] staging: iio: adc: new driver for AD7314 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 10/36] staging: iio: adc: new driver for AD7414/5 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 11/36] staging: iio: adc: new driver for AD7416/7/8 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 12/36] staging: iio: adc: new driver for AD7745/6/7 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 13/36] staging: iio: adc: new driver for AD7816 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 14/36] staging: iio: adc: new driver for ADT75 temperature sensors Mike Frysinger
2010-10-24 21:22 ` [PATCH 15/36] staging: iio: adc: new driver for ADT7310 " Mike Frysinger
2010-10-24 21:22 ` [PATCH 16/36] staging: iio: adc: new driver for ADT7408 " Mike Frysinger
2010-10-24 21:22 ` [PATCH 17/36] staging: iio: adc: new driver for ADT7410 " Mike Frysinger
2010-10-24 21:22 ` [PATCH 18/36] staging: iio: gyro: new driver for ADIS16261 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 19/36] staging: iio: gyro: new driver for ADIS16060 digital output gyros Mike Frysinger
2010-10-24 21:22 ` [PATCH 20/36] staging: iio: gyro: new driver for ADIS16080 " Mike Frysinger
2010-10-24 21:22 ` [PATCH 21/36] staging: iio: gyro: new driver for ADIS16130 " Mike Frysinger
2010-10-24 21:22 ` [PATCH 22/36] staging: iio: dac: new driver for AD5624R devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 23/36] staging: iio: dds: new driver for AD5930/2 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 24/36] staging: iio: dds: new driver for AD9832/3/4/5 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 25/36] staging: iio: dds: new driver for AD9850/1 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 26/36] staging: iio: dds: new driver for AD9852/4 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 27/36] staging: iio: dds: new driver for AD9910 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 28/36] staging: iio: dds: new driver for AD9951 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 29/36] staging: iio: meter: new driver for ADE7753/6 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 30/36] staging: iio: meter: new driver for ADE7754 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 31/36] staging: iio: meter: new driver for ADE7758 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 32/36] staging: iio: meter: new driver for ADE7759 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 33/36] staging: iio: meter: new driver for ADE7854/58/68/78 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 34/36] staging: iio: resolver: new driver for AD2S90 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 35/36] staging: iio: resolver: new driver for AD2S1200/1205 devices Mike Frysinger
2010-10-24 21:22 ` [PATCH 36/36] staging: iio: resolver: new driver for AD2S1210 devices Mike Frysinger
2010-10-24 21:35 ` [Device-drivers-devel] [PATCH 00/36] staging: iio: ADI drivers for staging-next Mike Frysinger
2010-10-24 23:41 ` Jonathan Cameron [this message]
2010-10-24 23:35 ` Jonathan Cameron
2010-10-24 23:45 ` [Device-drivers-devel] " Mike Frysinger
2010-10-25 8:39 ` Hennerich, Michael
2010-10-25 10:05 ` Jonathan Cameron
2010-10-25 10:35 ` Jonathan Cameron
2010-10-25 10:40 ` Hennerich, Michael
2010-10-26 0:53 ` Mike Frysinger
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=4CC4C442.5000304@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=linux-iio@vger.kernel.org \
--cc=vapier@gentoo.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.