From: Chris Ball <cjb@laptop.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Dong Aisheng <b29396@freescale.com>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
fengguang.wu@intel.com
Subject: Re: [PATCH 1/1] mmc: sdhci-of-esdhc: fix building error
Date: Fri, 27 Sep 2013 15:35:36 +0100 [thread overview]
Message-ID: <86eh8acoxz.fsf@void.printf.net> (raw)
In-Reply-To: <20130927052041.GH25146@S2101-09.ap.freescale.net> (Shawn Guo's message of "Fri, 27 Sep 2013 13:20:43 +0800")
Hi,
On Fri, Sep 27 2013, Shawn Guo wrote:
> I just compile-tested it with powerpc toolchain, so
>
> Tested-by: Shawn Guo <shawn.guo@linaro.org>
>
> Hi Chris,
>
> It's your call to apply it as a fix patch or amend it to the offending
> one. We're fine with either way.
Thanks, I've amended and pushed out to mmc-next now.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mmc: sdhci-of-esdhc: fix building error
Date: Fri, 27 Sep 2013 15:35:36 +0100 [thread overview]
Message-ID: <86eh8acoxz.fsf@void.printf.net> (raw)
In-Reply-To: <20130927052041.GH25146@S2101-09.ap.freescale.net> (Shawn Guo's message of "Fri, 27 Sep 2013 13:20:43 +0800")
Hi,
On Fri, Sep 27 2013, Shawn Guo wrote:
> I just compile-tested it with powerpc toolchain, so
>
> Tested-by: Shawn Guo <shawn.guo@linaro.org>
>
> Hi Chris,
>
> It's your call to apply it as a fix patch or amend it to the offending
> one. We're fine with either way.
Thanks, I've amended and pushed out to mmc-next now.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
next prev parent reply other threads:[~2013-09-27 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 4:00 [PATCH 1/1] mmc: sdhci-of-esdhc: fix building error Dong Aisheng
2013-09-27 4:00 ` Dong Aisheng
2013-09-27 5:20 ` Shawn Guo
2013-09-27 5:20 ` Shawn Guo
2013-09-27 14:35 ` Chris Ball [this message]
2013-09-27 14:35 ` 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=86eh8acoxz.fsf@void.printf.net \
--to=cjb@laptop.org \
--cc=b29396@freescale.com \
--cc=fengguang.wu@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.guo@linaro.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 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.