From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: <linux-mmc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <cjb@laptop.org>, <ludovic.desroches@atmel.com>,
<plagnioj@jcrosoft.com>, <arnd@arndb.de>, <olof@lixom.net>,
Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: [PATCH] ARM: at91/feature-removal-schedule: delay at91_mci removal
Date: Thu, 23 Aug 2012 15:27:28 +0200 [thread overview]
Message-ID: <1345728448-29384-1-git-send-email-nicolas.ferre@atmel.com> (raw)
From: Ludovic Desroches <ludovic.desroches@atmel.com>
Delay sd/mmc driver at91_mci.c removal because of tight schedule to
move platform data to new driver atmel-mci.
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
---
Hi,
I plan to queue this one with the at91-fixes pull-request for 3.6. If you do
not feel it is a good idea, please say so.
Documentation/feature-removal-schedule.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index afaff31..f4d8c71 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -579,7 +579,7 @@ Why: KVM tracepoints provide mostly equivalent information in a much more
----------------------------
What: at91-mci driver ("CONFIG_MMC_AT91")
-When: 3.7
+When: 3.8
Why: There are two mci drivers: at91-mci and atmel-mci. The PDC support
was added to atmel-mci as a first step to support more chips.
Then at91-mci was kept only for old IP versions (on at91rm9200 and
--
1.7.10
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: cjb@laptop.org, ludovic.desroches@atmel.com,
plagnioj@jcrosoft.com, arnd@arndb.de, olof@lixom.net,
Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: [PATCH] ARM: at91/feature-removal-schedule: delay at91_mci removal
Date: Thu, 23 Aug 2012 15:27:28 +0200 [thread overview]
Message-ID: <1345728448-29384-1-git-send-email-nicolas.ferre@atmel.com> (raw)
From: Ludovic Desroches <ludovic.desroches@atmel.com>
Delay sd/mmc driver at91_mci.c removal because of tight schedule to
move platform data to new driver atmel-mci.
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
---
Hi,
I plan to queue this one with the at91-fixes pull-request for 3.6. If you do
not feel it is a good idea, please say so.
Documentation/feature-removal-schedule.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index afaff31..f4d8c71 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -579,7 +579,7 @@ Why: KVM tracepoints provide mostly equivalent information in a much more
----------------------------
What: at91-mci driver ("CONFIG_MMC_AT91")
-When: 3.7
+When: 3.8
Why: There are two mci drivers: at91-mci and atmel-mci. The PDC support
was added to atmel-mci as a first step to support more chips.
Then at91-mci was kept only for old IP versions (on at91rm9200 and
--
1.7.10
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91/feature-removal-schedule: delay at91_mci removal
Date: Thu, 23 Aug 2012 15:27:28 +0200 [thread overview]
Message-ID: <1345728448-29384-1-git-send-email-nicolas.ferre@atmel.com> (raw)
From: Ludovic Desroches <ludovic.desroches@atmel.com>
Delay sd/mmc driver at91_mci.c removal because of tight schedule to
move platform data to new driver atmel-mci.
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
---
Hi,
I plan to queue this one with the at91-fixes pull-request for 3.6. If you do
not feel it is a good idea, please say so.
Documentation/feature-removal-schedule.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index afaff31..f4d8c71 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -579,7 +579,7 @@ Why: KVM tracepoints provide mostly equivalent information in a much more
----------------------------
What: at91-mci driver ("CONFIG_MMC_AT91")
-When: 3.7
+When: 3.8
Why: There are two mci drivers: at91-mci and atmel-mci. The PDC support
was added to atmel-mci as a first step to support more chips.
Then at91-mci was kept only for old IP versions (on at91rm9200 and
--
1.7.10
next reply other threads:[~2012-08-23 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 13:27 Nicolas Ferre [this message]
2012-08-23 13:27 ` [PATCH] ARM: at91/feature-removal-schedule: delay at91_mci removal Nicolas Ferre
2012-08-23 13:27 ` 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=1345728448-29384-1-git-send-email-nicolas.ferre@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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.