From: Wolfram Sang <w.sang@pengutronix.de>
To: Barry Song <21cnbao@gmail.com>
Cc: Chris Ball <cjb@laptop.org>,
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 08:58:51 +0200 [thread overview]
Message-ID: <20110426065851.GA14534@pengutronix.de> (raw)
In-Reply-To: <BANLkTimXXirF6zqx9h9DMRSpx+o8_vb=3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
> > * Where is the patch that implements the get_shared_pins() hook in
> > your driver?
> We send the common level patch ahead to get the upstream agreement so
> that we can maintain our bottom level sdhci codes better. We will send
> the special driver patch after some time.
Hmm, why should be there a functionality if there is no user for it? A
reference user helps people understand how it is intended to be used.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-26 6:58 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 [this message]
2011-04-26 7:27 ` Barry Song
2011-04-26 13:00 ` Chris Ball
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=20110426065851.GA14534@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=21cnbao@gmail.com \
--cc=Binghua.Duan@csr.com \
--cc=andreiw@motorola.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.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.