From: Scott Wood <scottwood@freescale.com>
To: Zhang Haijun <B42677@freescale.com>
Cc: linux-mmc@vger.kernel.org, cbouatmailru@gmail.com,
cjb@laptop.org, linuxppc-dev@lists.ozlabs.org,
Haijun Zhang <Haijun.Zhang@freescale.com>
Subject: Re: [PATCH 1/3 V2] mmc:core: parse voltage from device-tree
Date: Mon, 12 Aug 2013 11:11:29 -0500 [thread overview]
Message-ID: <1376323889.20487.7.camel@snotra.buserror.net> (raw)
In-Reply-To: <52084C7E.9000706@freescale.com>
On Mon, 2013-08-12 at 10:46 +0800, Zhang Haijun wrote:
> On 08/09/2013 10:48 PM, Kumar Gala wrote:
>
> > On Jul 31, 2013, at 1:25 AM, Haijun Zhang wrote:
> >
> > > Add function to support get voltage from device-tree.
> > > If there are voltage-range specified in device-tree node, this function
> > > will parse it and return the avail voltage mask.
> > >
> > > Signed-off-by: Haijun Zhang <haijun.zhang@freescale.com>
> > > ---
> > > changes for v2:
> > > - Update the parameters of function
> > >
> > > drivers/mmc/core/core.c | 46 ++++++++++++++++++++++++++++++++++++++++++++++
> > > include/linux/mmc/core.h | 1 +
> > > 2 files changed, 47 insertions(+)
> > There should be a device tree binding spec update to go with this patch series.
> >
> > - k
> Hi, kumar
>
> I'll update this tree binding spec after the patch set is accept by
> Anton.
Bindings should come first (or at least, at the same time).
-Scott
prev parent reply other threads:[~2013-08-12 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 6:25 [PATCH 1/3 V2] mmc:core: parse voltage from device-tree Haijun Zhang
2013-07-31 6:25 ` [PATCH 3/3 V2] mmc:esdhc: add support to get " Haijun Zhang
2013-07-31 6:25 ` [PATCH] mmc:of_spi: Update the code of getting voltage-ranges Haijun Zhang
2013-08-09 0:08 ` Anton Vorontsov
2013-08-07 1:28 ` [PATCH 1/3 V2] mmc:core: parse voltage from device-tree Zhang Haijun
2013-08-09 0:15 ` Anton Vorontsov
2013-08-09 3:34 ` Zhang Haijun
2013-08-09 14:48 ` Kumar Gala
2013-08-12 2:46 ` Zhang Haijun
2013-08-12 16:11 ` Scott Wood [this message]
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=1376323889.20487.7.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=B42677@freescale.com \
--cc=Haijun.Zhang@freescale.com \
--cc=cbouatmailru@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).