From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: platform data for atmel-mci (for 3.5)
Date: Mon, 4 Jun 2012 17:48:41 +0200 [thread overview]
Message-ID: <4FCCD8D9.2070005@atmel.com> (raw)
In-Reply-To: <CAOesGMhq8uzei+Dn8=1iYrTiAOtuByjm58j9zgFyORVG5VZuNQ@mail.gmail.com>
On 05/31/2012 11:04 PM, Olof Johansson :
> Hi Nicolas,
>
> On Thu, May 31, 2012 at 12:50 AM, Nicolas Ferre <nicolas.ferre@atmel.com
> <mailto:nicolas.ferre@atmel.com>> wrote:
>
> On 05/24/2012 05:12 PM, Nicolas Ferre :
> > Hi Arnd, hi Olof,
>
> Ping?
>
> (or maybe you will have a look at this after the merge window...)
>
>
> So, I looked at this branch yesterday but I wasn't entirely happy with
> the number of ifdefs it adds.
Unfortunately, this is the usual shape of any devices/boards files on
AT91. This amount will be reduced when we remove the old driver and when
we move newer/popular devices to Device Tree...
> If the idea is to deprecate the old driver, wouldn't it make more sense
> to just cut everyone over instead of having both sets of setup in the
> kernel?
Well, the old driver has existed since a very long time and I think that
people are used to it on oldest platforms. This is why we put in place a
overlapping period. This way we hope that the transition will be smoother.
On the other hand, the old code will be removed in 3.7 so the
overlapping period will not be so long.
I hope that it will allow people to track bugs if some are remaining and
switch to newer driver easily.
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2012-06-04 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 15:12 [GIT PULL] at91: platform data for atmel-mci (for 3.5) Nicolas Ferre
2012-05-31 7:50 ` Nicolas Ferre
2012-05-31 21:04 ` Olof Johansson
2012-06-04 15:48 ` Nicolas Ferre [this message]
2012-06-13 16:48 ` Nicolas Ferre
2012-06-18 13:49 ` Olof Johansson
2012-06-20 7:45 ` Nicolas Ferre
2012-07-25 20:06 ` Arnd Bergmann
2012-07-26 8:35 ` ludovic.desroches
2012-08-07 13:05 ` Nicolas Ferre
2012-08-10 7:46 ` Nicolas Ferre
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=4FCCD8D9.2070005@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.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).