From: Chris Ball <cjb@laptop.org>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: linux-mmc@vger.kernel.org,
'Jaehoon Chung' <jh80.chung@samsung.com>,
'Alim Akhtar' <alim.akhtar@samsung.com>
Subject: Re: [PATCH 00/22] mmc: dw_mmc: add driver's updates
Date: Tue, 03 Sep 2013 12:24:00 +0100 [thread overview]
Message-ID: <86r4d6b12n.fsf@void.printf.net> (raw)
In-Reply-To: <005601cea87c$7f0b9680$7d22c380$%jun@samsung.com> (Seungwon Jeon's message of "Tue, 03 Sep 2013 17:06:30 +0900")
Hi,
On Tue, Sep 03 2013, Seungwon Jeon wrote:
> Please could you apply this updates for mmc-next?
3.11 is released, so it's too late to apply these to the 3.12-rc1
merge, since there would be no time to test them in linux-next. But
it looks like many of them are fixes, so we can just send those later
in the 3.12 cycle.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
next prev parent reply other threads:[~2013-09-03 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 15:10 [PATCH 00/22] mmc: dw_mmc: add driver's updates Seungwon Jeon
2013-09-03 8:06 ` Seungwon Jeon
2013-09-03 11:24 ` Chris Ball [this message]
2013-09-26 1:37 ` 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=86r4d6b12n.fsf@void.printf.net \
--to=cjb@laptop.org \
--cc=alim.akhtar@samsung.com \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.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).