From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Ulf Hansson <ulf.hansson@stericsson.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Philip Rakity <prakity@marvell.com>,
Ulf Hansson <ulf.hansson@linaro.org>, Chris Ball <cjb@laptop.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v4] mmc: add a function to get regulators, supplying card's power
Date: Wed, 13 Jun 2012 17:26:59 +0800 [thread overview]
Message-ID: <20120613092658.GD4545@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1206131024300.17854@axis700.grange>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
On Wed, Jun 13, 2012 at 10:28:22AM +0200, Guennadi Liakhovetski wrote:
> I have no strong preference about this. Having an additional struct is how
> I interpreted Mark's proposal:
> http://thread.gmane.org/gmane.linux.kernel.mmc/14624/focus=14876
> but I'm also fine with putting it in mmc_host. Chris, what's your
> preference?
I'm just suggesting that because it seems like this is idiomatic for the
MMC API.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-13 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 15:57 [PATCH v4] mmc: add a function to get regulators, supplying card's power Guennadi Liakhovetski
2012-06-12 16:40 ` Philip Rakity
2012-06-12 16:52 ` Guennadi Liakhovetski
2012-06-12 23:00 ` Philip Rakity
2012-06-13 7:58 ` Guennadi Liakhovetski
2012-06-13 8:22 ` Ulf Hansson
2012-06-13 8:28 ` Guennadi Liakhovetski
2012-06-13 9:26 ` Mark Brown [this message]
2012-06-13 9:40 ` 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=20120613092658.GD4545@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=adrian.hunter@intel.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prakity@marvell.com \
--cc=ulf.hansson@linaro.org \
--cc=ulf.hansson@stericsson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox