From: Chris Ball <cjb@laptop.org>
To: Barry Song <21cnbao@gmail.com>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
linux-mmc@vger.kernel.org, Binghua.Duan@csr.com,
andreiw@motorola.com, prakity@marvell.com
Subject: Re: [PATCH] mmc:sdhci:add support to request/free pins for controllers sharing hardware bus
Date: Tue, 26 Apr 2011 09:00:40 -0400 [thread overview]
Message-ID: <m3pqo9rwuf.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <BANLkTineayh539zJx6GfxnpgCJwJdxYy0Q@mail.gmail.com> (Barry Song's message of "Tue, 26 Apr 2011 15:27:28 +0800")
Hi Barry,
On Tue, Apr 26 2011, Barry Song wrote:
> Just because Our SoCs are still on the way to opensource and mainline.
> Even our arch/arm/mach-xxx hasn't been merged yet. Our target is
> syncing our codes with mainline. So as a modification to sdhci common
> level, we just get upstream's opinion for local maintaining earlier.
>
> Anyway, this patch may be applied later after our others are ready. Or
> it can be now so that other SoC companies can use this feature.
Thanks for the explanation. In that case, I'll give you my Reviewed-by:
on the patch now, but will wait to merge it until you have your driver
support code posted too. (Or until, as you say, someone else would like
the same hook.)
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-04-26 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5EB3BFCD089AD643B9BB63439F5FD5E9A127@SHAASIEXM01.ASIA.ROOT.PRI>
2011-04-26 3:34 ` [PATCH] mmc:sdhci:add support to request/free pins for controllers sharing hardware bus Barry Song
2011-04-26 3:48 ` Chris Ball
2011-04-26 3:50 ` Barry Song
2011-04-26 6:58 ` Wolfram Sang
2011-04-26 7:27 ` Barry Song
2011-04-26 13:00 ` Chris Ball [this message]
2011-04-26 15:28 ` Philip Rakity
2011-04-28 1:14 ` Barry Song
2011-04-28 1:16 ` Barry Song
2011-04-26 3:48 ` Philip Rakity
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=m3pqo9rwuf.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=21cnbao@gmail.com \
--cc=Binghua.Duan@csr.com \
--cc=andreiw@motorola.com \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox