From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH 3/4 v3] mmc: sh_mmcif: process requests asynchronously
Date: Mon, 26 Dec 2011 12:59:52 -0500 [thread overview]
Message-ID: <m2boqvjjs7.fsf@bob.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1112260942330.9178@axis700.grange> (Guennadi Liakhovetski's message of "Mon, 26 Dec 2011 09:44:32 +0100 (CET)")
Hi,
On Mon, Dec 26 2011, Guennadi Liakhovetski wrote:
> I can resend it if you like, but in fact that fuzz is harmless - you can
> go ahead with the patch you have at hand. But, please, do let me know if
> you prefer to have an updated patch.
Okay, pushed to mmc-next for 3.3 -- please just check everything looks
reasonable there. Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-12-26 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 15:07 [PATCH] mmc: sh_mmcif: process requests asynchronously Guennadi Liakhovetski
2011-12-02 15:24 ` Magnus Damm
2011-12-02 15:54 ` Guennadi Liakhovetski
2011-12-14 18:31 ` [PATCH 0/4 v2] mmc_ " Guennadi Liakhovetski
2011-12-14 18:31 ` [PATCH 1/4] mmc: sh_mmcif: process error interrupts first Guennadi Liakhovetski
2011-12-14 18:31 ` [PATCH 2/4 v2] mmc: sh_mmcif: cosmetic clean up Guennadi Liakhovetski
2011-12-14 18:31 ` [PATCH 3/4 v2] mmc: sh_mmcif: process requests asynchronously Guennadi Liakhovetski
2011-12-25 2:20 ` Chris Ball
2011-12-25 20:07 ` [PATCH 3/4 v3] " Guennadi Liakhovetski
2011-12-25 22:43 ` Chris Ball
2011-12-25 23:00 ` Guennadi Liakhovetski
2011-12-26 1:48 ` Chris Ball
2011-12-26 8:44 ` Guennadi Liakhovetski
2011-12-26 17:59 ` Chris Ball [this message]
2011-12-14 18:31 ` [PATCH 4/4] mmc: sh_mmcif: remove now superfluous sh_mmcif_host::data member Guennadi Liakhovetski
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=m2boqvjjs7.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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