All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Chris Ball <cjb@laptop.org>,
	linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: linux-mmc@vger.kernel.org,
	"ludovic.desroches" <ludovic.desroches@atmel.com>,
	plagnioj@jcrosoft.com
Subject: Re: [PATCH 2/2] mmc: at91-mci: this driver is now deprecated
Date: Mon, 21 May 2012 12:19:49 +0200	[thread overview]
Message-ID: <4FBA16C5.30206@atmel.com> (raw)
In-Reply-To: <87pqa21wow.fsf@laptop.org>

On 05/17/2012 08:36 PM, Chris Ball :
> Hi,
> 
> On Thu, May 17 2012, ludovic.desroches wrote:
>>>> +	  remove soon (for more information have a look to
>>>            ^ removed
>>>> +	  Documentation/feature-removal-schedule.txt). Please use
>>>> +	  MMC_ATMEL_MCI.
>>>>
>>>>   	  If unsure, say N.
>>
>> Sorry for the typo, do you want a new patch or is ok?
> 
> It's okay, I've fixed it up here.
> 
>>> Seems like I should take this patch 2/2, and then someone else should
>>> merge 1/2?
>>
>> Yes, Nicolas would probably take patch 2/2.
> 
> I think you must mean that Nicolas takes 1/2 (the arch/arm/ patches).
> Assuming you do, that's fine and I've pushed 2/2 to mmc-next for 3.5 now.

Ludovic and Chris,

Sure, I will take 1/2 patch of this series through arm-soc.
Unfortunately, it seems to be a bit late for 3.5...

Anyway, I will talk with Arnd and Olof about the possibility to include
it in a "late" or "staging" branch: that will allow this platform data
addition to have some exposure in linux-next.
We can also imagine that having a better support for atmel-mci driver in
AT91 boards will help people gain a more stable system and avoid using a
now "deprecated" driver that will be removed in 3.7. So I am personally
in favor for an inclusion as soon as possible...

Thanks, best regards,
-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mmc: at91-mci: this driver is now deprecated
Date: Mon, 21 May 2012 12:19:49 +0200	[thread overview]
Message-ID: <4FBA16C5.30206@atmel.com> (raw)
In-Reply-To: <87pqa21wow.fsf@laptop.org>

On 05/17/2012 08:36 PM, Chris Ball :
> Hi,
> 
> On Thu, May 17 2012, ludovic.desroches wrote:
>>>> +	  remove soon (for more information have a look to
>>>            ^ removed
>>>> +	  Documentation/feature-removal-schedule.txt). Please use
>>>> +	  MMC_ATMEL_MCI.
>>>>
>>>>   	  If unsure, say N.
>>
>> Sorry for the typo, do you want a new patch or is ok?
> 
> It's okay, I've fixed it up here.
> 
>>> Seems like I should take this patch 2/2, and then someone else should
>>> merge 1/2?
>>
>> Yes, Nicolas would probably take patch 2/2.
> 
> I think you must mean that Nicolas takes 1/2 (the arch/arm/ patches).
> Assuming you do, that's fine and I've pushed 2/2 to mmc-next for 3.5 now.

Ludovic and Chris,

Sure, I will take 1/2 patch of this series through arm-soc.
Unfortunately, it seems to be a bit late for 3.5...

Anyway, I will talk with Arnd and Olof about the possibility to include
it in a "late" or "staging" branch: that will allow this platform data
addition to have some exposure in linux-next.
We can also imagine that having a better support for atmel-mci driver in
AT91 boards will help people gain a more stable system and avoid using a
now "deprecated" driver that will be removed in 3.7. So I am personally
in favor for an inclusion as soon as possible...

Thanks, best regards,
-- 
Nicolas Ferre

  parent reply	other threads:[~2012-05-21 10:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 15:51 [PATCH 0/2] ARM: at91: allow all boards to use atmel-mci driver ludovic.desroches
2012-05-16 15:51 ` ludovic.desroches at atmel.com
2012-05-16 15:51 ` [PATCH 1/2] ARM: at91: add atmel-mci support for chips and boards which can use it ludovic.desroches
2012-05-16 15:51   ` ludovic.desroches at atmel.com
2012-05-21 10:17   ` Nicolas Ferre
2012-05-21 10:17     ` Nicolas Ferre
2012-05-16 15:51 ` [PATCH 2/2] mmc: at91-mci: this driver is now deprecated ludovic.desroches
2012-05-16 15:51   ` ludovic.desroches at atmel.com
2012-05-17 12:45   ` Chris Ball
2012-05-17 12:45     ` Chris Ball
2012-05-17 18:28     ` ludovic.desroches
2012-05-17 18:28       ` ludovic.desroches
2012-05-17 18:36       ` Chris Ball
2012-05-17 18:36         ` Chris Ball
2012-05-17 18:40         ` ludovic.desroches
2012-05-17 18:40           ` ludovic.desroches
2012-05-21 10:19         ` Nicolas Ferre [this message]
2012-05-21 10:19           ` Nicolas Ferre
2012-05-21 10:23   ` [PATCH v2] ARM: at91: add atmel-mci support for chips and boards which can use it ludovic.desroches
2012-05-21 10:23     ` ludovic.desroches at atmel.com
2012-05-21 10:31     ` ludovic.desroches
2012-05-21 10:31       ` ludovic.desroches
2012-05-28  7:41     ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-28  7:41       ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-29 10:56       ` Nicolas Ferre
2012-05-29 10:56         ` Nicolas Ferre
2012-05-29 15:57         ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-29 15:57           ` Jean-Christophe PLAGNIOL-VILLARD

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=4FBA16C5.30206@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=arnd@arndb.de \
    --cc=cjb@laptop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=olof@lixom.net \
    --cc=plagnioj@jcrosoft.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.