From: Chris Ball <cjb@laptop.org>
To: Ian Molton <ian@mnementh.co.uk>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-mmc@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
Andrew Morton <akpm@linux-foundation.org>,
Magnus Damm <damm@opensource.se>,
linux-sh@vger.kernel.org
Subject: Re: outstanding TMIO MMC patches
Date: Wed, 05 Jan 2011 22:57:03 +0000 [thread overview]
Message-ID: <20110105225703.GD13209@void.printf.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1012281211560.21647@axis700.grange>
Hi Ian,
On Wed, Dec 29, 2010 at 12:32:13AM +0100, Guennadi Liakhovetski wrote:
> There are a number of outstanding tmio-mmc patches from Arnd Hannemann and
> myself, many of them posted weeks ago. We really would like to have them
> in 2.6.38. Would you have time to process them? Otherwise, could someone
> else maybe apply them? Listed in the order, in which they should be
> applied.
I've applied these to mmc-next, plus two more of Arnd's, since it looks
like you don't have time for reviews at the moment. Feel free to review
them before .38 releases; we can still make changes if necessary. It'd
be great if you can retest on mmc-next with your HW, too.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2011-01-05 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 23:32 outstanding TMIO MMC patches Guennadi Liakhovetski
2010-12-29 13:35 ` Arnd Hannemann
2011-01-05 22:24 ` Chris Ball
2011-01-05 22:49 ` Chris Ball
2011-01-05 2:10 ` Magnus Damm
2011-01-05 4:53 ` Paul Mundt
2011-01-05 16:57 ` Chris Ball
2011-01-05 17:30 ` Paul Mundt
2011-01-05 18:57 ` Chris Ball
2011-01-05 21:16 ` Arnd Hannemann
2011-01-05 23:08 ` Paul Mundt
2011-01-05 23:31 ` Paul Mundt
2011-01-06 1:57 ` Magnus Damm
2011-01-05 22:57 ` 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=20110105225703.GD13209@void.printf.net \
--to=cjb@laptop.org \
--cc=akpm@linux-foundation.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.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).