From: Chris Ball <cjb@laptop.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Yauhen Kharuzhy <yauhen.kharuzhy@promwad.com>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MMC: Fix multiblock SDIO transfers in AT91 MCI
Date: Fri, 10 Dec 2010 16:23:51 +0000 [thread overview]
Message-ID: <20101210162351.GA11798@void.printf.net> (raw)
In-Reply-To: <4D024D25.2000501@atmel.com>
Hi Nicolas,
On Fri, Dec 10, 2010 at 04:54:13PM +0100, Nicolas Ferre wrote:
> A little "ping"!
>
> Do you want that I re-send you the patch with relevant S-O-B lines or
> you can include them yourself?
Thanks for the ping -- I've pushed this to mmc-next and queued it for
2.6.37 now. This looks like a candidate for the stable kernel to me;
do you agree?
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MMC: Fix multiblock SDIO transfers in AT91 MCI
Date: Fri, 10 Dec 2010 16:23:51 +0000 [thread overview]
Message-ID: <20101210162351.GA11798@void.printf.net> (raw)
In-Reply-To: <4D024D25.2000501@atmel.com>
Hi Nicolas,
On Fri, Dec 10, 2010 at 04:54:13PM +0100, Nicolas Ferre wrote:
> A little "ping"!
>
> Do you want that I re-send you the patch with relevant S-O-B lines or
> you can include them yourself?
Thanks for the ping -- I've pushed this to mmc-next and queued it for
2.6.37 now. This looks like a candidate for the stable kernel to me;
do you agree?
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-12-10 16:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 10:11 [PATCH] MMC: Fix multiblock SDIO transfers in AT91 MCI Yauhen Kharuzhy
2010-11-25 10:11 ` Yauhen Kharuzhy
2010-11-26 11:17 ` Nicolas Ferre
2010-11-26 11:17 ` Nicolas Ferre
2010-12-10 15:54 ` Nicolas Ferre
2010-12-10 15:54 ` Nicolas Ferre
2010-12-10 16:23 ` Chris Ball [this message]
2010-12-10 16:23 ` Chris Ball
2010-12-10 18:14 ` [PATCH] MMC: Fix multiblock SDIO transfers in ATMEL MCI Nicolas Ferre
2010-12-10 18:14 ` Nicolas Ferre
2010-12-10 17:21 ` Chris Ball
2010-12-10 17:21 ` Chris Ball
2010-12-12 0:42 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-12 0:42 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-12 1:13 ` Chris Ball
2010-12-12 1:13 ` Chris Ball
2010-11-26 19:46 ` [PATCH] MMC: Fix multiblock SDIO transfers in AT91 MCI Jean-Christophe PLAGNIOL-VILLARD
2010-11-26 19:46 ` Jean-Christophe PLAGNIOL-VILLARD
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=20101210162351.GA11798@void.printf.net \
--to=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=yauhen.kharuzhy@promwad.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 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.