From: Chris Ball <cjb@laptop.org>
To: Shawn Guo <shawn.guo@freescale.com>
Cc: patches@linaro.org, Sascha Hauer <s.hauer@pengutronix.de>,
linux-mmc@vger.kernel.org, Wolfram Sang <w.sang@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
Eric Benard <eric@eukrea.com>,
Philip Rakity <prakity@marvell.com>,
Arnaud Patard <arnaud.patard@rtp-net.org>
Subject: Re: [PATCH v4 0/4] Extend sdhci-esdhc-imx card_detect and write_protect support for mx5
Date: Fri, 01 Jul 2011 19:06:54 -0400 [thread overview]
Message-ID: <m2liwh4n3l.fsf@bob.laptop.org> (raw)
In-Reply-To: <20110627042345.GA21757@S2100-06.ap.freescale.net> (Shawn Guo's message of "Mon, 27 Jun 2011 12:23:46 +0800")
Hi,
On Mon, Jun 27 2011, Shawn Guo wrote:
>> I'll need to rebase mmc-next onto linux-next before I can merge it,
>> because the mach-imx/ board files you're modifying do not exist in
>> Linus' tree. (I don't mind doing that, but it might be easier if
>> you had the ARM patches go in via a different tree instead.)
>
> I can ask Sascha to pick up patch #4 with your ack. But the problem
> is patch #4 has to work with #1 applied first, otherwise the CD
> interrupt storm will freeze the system.
Let's do that, please. I've merged #1-#3 to mmc-next, and for #4:
Acked-by: Chris Ball <cjb@laptop.org>
(Sascha, please note that you'll have to send #4 to Linus after I send
the MMC pull request, as Shawn explains above.)
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] Extend sdhci-esdhc-imx card_detect and write_protect support for mx5
Date: Fri, 01 Jul 2011 19:06:54 -0400 [thread overview]
Message-ID: <m2liwh4n3l.fsf@bob.laptop.org> (raw)
In-Reply-To: <20110627042345.GA21757@S2100-06.ap.freescale.net> (Shawn Guo's message of "Mon, 27 Jun 2011 12:23:46 +0800")
Hi,
On Mon, Jun 27 2011, Shawn Guo wrote:
>> I'll need to rebase mmc-next onto linux-next before I can merge it,
>> because the mach-imx/ board files you're modifying do not exist in
>> Linus' tree. (I don't mind doing that, but it might be easier if
>> you had the ARM patches go in via a different tree instead.)
>
> I can ask Sascha to pick up patch #4 with your ack. But the problem
> is patch #4 has to work with #1 applied first, otherwise the CD
> interrupt storm will freeze the system.
Let's do that, please. I've merged #1-#3 to mmc-next, and for #4:
Acked-by: Chris Ball <cjb@laptop.org>
(Sascha, please note that you'll have to send #4 to Linus after I send
the MMC pull request, as Shawn explains above.)
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-07-01 23:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 14:41 [PATCH v4 0/4] Extend sdhci-esdhc-imx card_detect and write_protect support for mx5 Shawn Guo
2011-06-21 14:41 ` Shawn Guo
2011-06-21 14:41 ` [PATCH v4 1/4] mmc: sdhci: fix interrupt storm from card detection Shawn Guo
2011-06-21 14:41 ` Shawn Guo
2011-06-21 16:05 ` Philip Rakity
2011-06-21 16:05 ` Philip Rakity
2011-06-22 4:40 ` Shawn Guo
2011-06-22 4:40 ` Shawn Guo
2011-06-22 4:41 ` Philip Rakity
2011-06-22 4:41 ` Philip Rakity
2011-06-21 14:41 ` [PATCH v4 2/4] mmc: sdhci-esdhc-imx: SDHCI_CARD_PRESENT does not get cleared Shawn Guo
2011-06-21 14:41 ` Shawn Guo
2011-06-21 14:41 ` [PATCH v4 3/4] mmc: sdhci-esdhc-imx: remove "WP" from flag ESDHC_FLAG_GPIO_FOR_CD_WP Shawn Guo
2011-06-21 14:41 ` Shawn Guo
2011-06-21 14:41 ` [PATCH v4 4/4] mmc: sdhci-esdhc-imx: extend card_detect and write_protect support for mx5 Shawn Guo
2011-06-21 14:41 ` Shawn Guo
2011-06-27 1:38 ` [PATCH v4 0/4] Extend sdhci-esdhc-imx " Shawn Guo
2011-06-27 1:38 ` Shawn Guo
2011-06-27 3:47 ` Chris Ball
2011-06-27 3:47 ` Chris Ball
2011-06-27 4:23 ` Shawn Guo
2011-06-27 4:23 ` Shawn Guo
2011-07-01 23:06 ` Chris Ball [this message]
2011-07-01 23:06 ` Chris Ball
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=m2liwh4n3l.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=arnaud.patard@rtp-net.org \
--cc=eric@eukrea.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=prakity@marvell.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@freescale.com \
--cc=w.sang@pengutronix.de \
/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.