From: Sascha Hauer <s.hauer@pengutronix.de>
To: Chris Ball <cjb@laptop.org>
Cc: Shawn Guo <shawn.guo@freescale.com>,
Shawn Guo <shawn.guo@linaro.org>,
linux-mmc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, patches@linaro.org
Subject: Re: [PATCH v3 0/4] Add device tree probe for sdhci-esdhc-imx
Date: Tue, 19 Jul 2011 10:10:27 +0200 [thread overview]
Message-ID: <20110719081027.GM20587@pengutronix.de> (raw)
In-Reply-To: <m262mzavhb.fsf@bob.laptop.org>
On Mon, Jul 18, 2011 at 09:51:28PM -0400, Chris Ball wrote:
> Hi Shawn, Sascha,
>
> On Sat, Jul 09 2011, Shawn Guo wrote:
> >> > Shawn Guo (4):
> >> > mmc: sdhci-esdhc-imx: do not reference platform data after probe
> >> > mmc: sdhci-esdhc-imx: get rid of the uses of cpu_is_mx()
> >> > mmc: sdhci-pltfm: dt device does not pass parent to sdhci_alloc_host
> >> > mmc: sdhci-esdhc-imx: add device tree probe support
> >>
> >> These don't apply against mmc-next -- what is your tree based on?
> >>
> > It's based on linux-next with following patch applied.
> >
> > [PATCH v4 4/4] mmc: sdhci-esdhc-imx: extend card_detect and
> > write_protect support for mx5
> > http://permalink.gmane.org/gmane.linux.kernel.mmc/8748
> >
> > You applied the 3 of 4 patches in that series, and expect Sascha to
> > send this one through his tree after you send those 3.
Shawn, please ping me once all dependencies have been merged. I have no
influence when my patches get merged since my patches go via Arnd.
>
> I see. In that case, either Sascha can send this new series with my:
>
> Acked-by: Chris Ball <cjb@laptop.org>
>
> or I'll send it as a second pull request after Sascha sends [4/4].
>
> Thanks,
>
> - Chris.
> --
> Chris Ball <cjb@laptop.org> <http://printf.net/>
> One Laptop Per Child
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-07-19 8:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:47 [PATCH v3 0/4] Add device tree probe for sdhci-esdhc-imx Shawn Guo
2011-07-06 16:47 ` [PATCH v3 1/4] mmc: sdhci-esdhc-imx: do not reference platform data after probe Shawn Guo
2011-07-06 21:03 ` Grant Likely
2011-07-06 16:47 ` [PATCH v3 2/4] mmc: sdhci-esdhc-imx: get rid of the uses of cpu_is_mx() Shawn Guo
2011-07-06 16:47 ` [PATCH v3 3/4] mmc: sdhci-pltfm: dt device does not pass parent to sdhci_alloc_host Shawn Guo
2011-07-06 16:47 ` [PATCH v3 4/4] mmc: sdhci-esdhc-imx: add device tree probe support Shawn Guo
2011-07-06 21:05 ` Grant Likely
2011-07-13 15:52 ` Anton Vorontsov
2011-07-13 16:09 ` Scott Wood
2011-07-13 16:28 ` Anton Vorontsov
2011-07-13 16:36 ` Grant Likely
2011-07-13 17:32 ` Anton Vorontsov
2011-07-09 22:14 ` [PATCH v3 0/4] Add device tree probe for sdhci-esdhc-imx Chris Ball
2011-07-10 1:37 ` Shawn Guo
2011-07-19 1:51 ` Chris Ball
2011-07-19 8:10 ` Sascha Hauer [this message]
2011-07-19 8:59 ` Shawn Guo
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=20110719081027.GM20587@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=shawn.guo@freescale.com \
--cc=shawn.guo@linaro.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).