From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Jonathan Cameron <jic23@cam.ac.uk>,
Olof Johansson <olof@lixom.net>,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
thomas@free-electrons.com, patrice.vilchez@atmel.com,
plagnioj@jcrosoft.com
Subject: Re: [PATCHv3] Add ADC driver for Atmel G20, G45 and X5 boards
Date: Wed, 9 May 2012 14:46:40 +0000 [thread overview]
Message-ID: <201205091446.40849.arnd@arndb.de> (raw)
In-Reply-To: <4FAA7CB6.8030506@atmel.com>
On Wednesday 09 May 2012, Nicolas Ferre wrote:
> Jonathan, Arnd, Olof,
>
> As explained by Maxime, this patch series is adding the Atmel ADC driver
> to the out-of-staging iio subsystem. It relies on patches that are in
> staging-next.
> On the other hand, I really wouldn't like to split the series between
> iio and arm-soc...
> My question is: would it be possible to take this series in Jonathan
> iio/staging-next git tree for inclusion in 3.5? Arnd & Olof, is it ok
> for you? Do you want to add your Acked-by on some patches?
Hmm, if we would do only the DT-based probing for this, it would be
very simple to split the patches between the two branches, but with
the dependency on the platform_data definition, we can't do that.
If you think we still need the platform_data, I guess it can go in
the iio tree, but I'd be happier if we didn't need it any more.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] Add ADC driver for Atmel G20, G45 and X5 boards
Date: Wed, 9 May 2012 14:46:40 +0000 [thread overview]
Message-ID: <201205091446.40849.arnd@arndb.de> (raw)
In-Reply-To: <4FAA7CB6.8030506@atmel.com>
On Wednesday 09 May 2012, Nicolas Ferre wrote:
> Jonathan, Arnd, Olof,
>
> As explained by Maxime, this patch series is adding the Atmel ADC driver
> to the out-of-staging iio subsystem. It relies on patches that are in
> staging-next.
> On the other hand, I really wouldn't like to split the series between
> iio and arm-soc...
> My question is: would it be possible to take this series in Jonathan
> iio/staging-next git tree for inclusion in 3.5? Arnd & Olof, is it ok
> for you? Do you want to add your Acked-by on some patches?
Hmm, if we would do only the DT-based probing for this, it would be
very simple to split the patches between the two branches, but with
the dependency on the platform_data definition, we can't do that.
If you think we still need the platform_data, I guess it can go in
the iio tree, but I'd be happier if we didn't need it any more.
Arnd
next prev parent reply other threads:[~2012-05-09 14:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 9:05 [PATCHv3] Add ADC driver for Atmel G20, G45 and X5 boards Maxime Ripard
2012-05-09 9:05 ` Maxime Ripard
2012-05-09 9:05 ` [PATCH 1/9] ARM: AT91: Add platform data for the AT91 ADCs Maxime Ripard
2012-05-09 9:05 ` Maxime Ripard
2012-05-09 13:04 ` Jonathan Cameron
2012-05-09 13:04 ` Jonathan Cameron
2012-05-09 9:05 ` [PATCH 2/9] ARM: AT91: IIO: Add AT91 ADC driver Maxime Ripard
2012-05-09 9:05 ` Maxime Ripard
2012-05-09 9:06 ` [PATCH 3/9] ARM: AT91: Add the ADC to the sam9g20ek board Maxime Ripard
2012-05-09 9:06 ` Maxime Ripard
2012-05-09 9:06 ` [PATCH 4/9] IIO: AT91: ADC: Add support for the AT91SAM9M10G45-EK board Maxime Ripard
2012-05-09 9:06 ` Maxime Ripard
2012-05-09 9:06 ` [PATCH 5/9] Add clocks for X5 boards Maxime Ripard
2012-05-09 9:06 ` Maxime Ripard
2012-05-09 9:06 ` [PATCH 6/9] IIO: AT91: Add DT support to at91_adc driver Maxime Ripard
2012-05-09 9:06 ` Maxime Ripard
2012-05-09 9:06 ` [PATCH 7/9] Add ADC driver to the at91sam9g45 dtsi Maxime Ripard
2012-05-09 9:06 ` Maxime Ripard
2012-05-09 9:06 ` [PATCH 8/9] Add ADC driver to the at91sam9x5 dtsi Maxime Ripard
2012-05-09 9:06 ` Maxime Ripard
2012-05-09 9:06 ` [PATCH 9/9] Add DTSI for the G20 SoC Maxime Ripard
2012-05-09 9:06 ` Maxime Ripard
2012-05-09 14:18 ` [PATCHv3] Add ADC driver for Atmel G20, G45 and X5 boards Nicolas Ferre
2012-05-09 14:18 ` Nicolas Ferre
2012-05-09 14:46 ` Arnd Bergmann [this message]
2012-05-09 14:46 ` Arnd Bergmann
2012-05-09 14:40 ` Arnd Bergmann
2012-05-09 14:40 ` Arnd Bergmann
2012-05-10 8:32 ` Maxime Ripard
2012-05-10 8:32 ` Maxime Ripard
2012-05-10 8:50 ` Nicolas Ferre
2012-05-10 8:50 ` Nicolas Ferre
2012-05-10 13:28 ` Arnd Bergmann
2012-05-10 13:28 ` Arnd Bergmann
2012-05-11 7:54 ` Maxime Ripard
2012-05-11 7:54 ` Maxime Ripard
2012-05-11 12:26 ` Jonathan Cameron
2012-05-11 12:26 ` 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=201205091446.40849.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
--cc=patrice.vilchez@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=thomas@free-electrons.com \
/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.