linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Haijun <B42677@freescale.com>
To: Chris Ball <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org,
	Haijun Zhang <Haijun.Zhang@freescale.com>,
	cbouatmailru@gmail.com, scottwood@freescale.com,
	linuxppc-dev@lists.ozlabs.org, X.Xie@freescale.com
Subject: Re: [PATCH V3] mmc:of_spi: Update the code of getting voltage-ranges
Date: Mon, 26 Aug 2013 09:05:16 +0800	[thread overview]
Message-ID: <521AA9CC.2090403@freescale.com> (raw)
In-Reply-To: <87txiepflk.fsf@octavius.laptop.org>

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

On 08/25/2013 12:19 PM, Chris Ball wrote:
> Hi Haijun,
>
> On Sun, Aug 11 2013, Haijun Zhang wrote:
>> Using function mmc_of_parse_voltage() to get voltage-ranges.
>>
>> Signed-off-by: Haijun Zhang <haijun.zhang@freescale.com>
> The patchset contains patches 1-3 of 3, and also this unnumbered patch
> v3.  Which order should I use to apply this patch?
>
> Thanks,
>
> - Chris.

Thanks Chris,

So, I'll numbered them an resend them to you.

Thanks a lot.

-- 
Thanks & Regards

Haijun


[-- Attachment #2: Type: text/html, Size: 1320 bytes --]

  reply	other threads:[~2013-08-26  1:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12  1:39 [PATCH 1/3 V4] mmc:core: parse voltage from device-tree Haijun Zhang
2013-08-12  1:39 ` [PATCH 3/3 V3] mmc:esdhc: add support to get " Haijun Zhang
2013-08-23  1:46   ` Anton Vorontsov
2013-08-12  1:39 ` [PATCH V3] mmc:of_spi: Update the code of getting voltage-ranges Haijun Zhang
2013-08-23  1:45   ` Anton Vorontsov
2013-08-25  4:19   ` Chris Ball
2013-08-26  1:05     ` Zhang Haijun [this message]
2013-08-12  1:39 ` [PATCH 2/3 V3] mmc:sdhc: get voltage from sdhc host Haijun Zhang
2013-08-23  1:48   ` Anton Vorontsov
2013-08-23  2:01     ` Zhang Haijun
2013-08-23  5:08     ` Zhang Haijun
2013-08-20  1:10 ` [PATCH 1/3 V4] mmc:core: parse voltage from device-tree Zhang Haijun

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=521AA9CC.2090403@freescale.com \
    --to=b42677@freescale.com \
    --cc=Haijun.Zhang@freescale.com \
    --cc=X.Xie@freescale.com \
    --cc=cbouatmailru@gmail.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).