From: ludovic.desroches@atmel.com (ludovic.desroches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mmc: at91-mci: this driver is now deprecated
Date: Thu, 17 May 2012 20:40:18 +0200 [thread overview]
Message-ID: <4FB54612.7090705@atmel.com> (raw)
In-Reply-To: <87pqa21wow.fsf@laptop.org>
Le 05/17/2012 08:36 PM, Chris Ball a ?crit :
> 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.
>
> Thanks,
>
> - Chris.
Fine. Thanks
Ludovic
next prev parent reply other threads:[~2012-05-17 18:40 UTC|newest]
Thread overview: 14+ 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 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 at atmel.com
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 at atmel.com
2012-05-17 12:45 ` Chris Ball
2012-05-17 18:28 ` ludovic.desroches
2012-05-17 18:36 ` Chris Ball
2012-05-17 18:40 ` ludovic.desroches [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 at atmel.com
2012-05-21 10:31 ` ludovic.desroches
2012-05-28 7:41 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-29 10:56 ` Nicolas Ferre
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=4FB54612.7090705@atmel.com \
--to=ludovic.desroches@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).