From: Chris Ball <chris@printf.net>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [GIT PULL] MMC updates for mmc-next for 3.15, take 1
Date: Sun, 23 Feb 2014 15:43:03 +0000 [thread overview]
Message-ID: <86vbw5sum0.fsf@void.printf.net> (raw)
In-Reply-To: <CAPDyKFrQKMMimNFr-3h+Em+W+A00tmS2mCxNUbkvyyZfom8+nA@mail.gmail.com> (Ulf Hansson's message of "Sun, 23 Feb 2014 16:33:31 +0100")
Hi Ulf,
On Sun, Feb 23 2014, Ulf Hansson wrote:
> I would suggest we go ahead and merge this for 3.15, unless you have
> any concerns with any of the patches of course.
Okay, pushed to mmc-next for 3.15. Thanks!
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
prev parent reply other threads:[~2014-02-23 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 11:09 [GIT PULL] MMC updates for mmc-next for 3.15, take 1 Ulf Hansson
2014-02-23 15:33 ` Ulf Hansson
2014-02-23 15:43 ` Chris Ball [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=86vbw5sum0.fsf@void.printf.net \
--to=chris@printf.net \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ulf.hansson@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 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).