All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	yauhen.kharuzhy@promwad.com
Subject: Re: [PATCH] MMC: Fix multiblock SDIO transfers in ATMEL MCI
Date: Fri, 10 Dec 2010 17:21:04 +0000	[thread overview]
Message-ID: <20101210172104.GA12871@void.printf.net> (raw)
In-Reply-To: <1292004872-5122-1-git-send-email-nicolas.ferre@atmel.com>

Hi Nicolas,

On Fri, Dec 10, 2010 at 07:14:32PM +0100, Nicolas Ferre wrote:
> Based on report made by Yauhen in:
> "MMC: Fix multiblock SDIO transfers in AT91 MCI" patch,
> I report those changes to the brother driver: atmel-mci.
> 
> So, this patch sets SDIO transfer types: SDIO block and SDIO byte
> transfers instead of using ordinary MMC block transfers.
> It is checking opcode for SDIO CMD53 and setting transfer
> type in MCI_CMDR register properly.
> 
> Reported-by: Yauhen Kharuzhy <yauhen.kharuzhy@promwad.com>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> 
> Hi Chris,
> 
> In addition to the at91_mci multiblock SDIO fix, I add this little one too as
> it concerns the brother driver atmel-mci with same issue.
> 
> I hope that you will be able to queue those fixes to .37-final and stable...

That's fine, this is queued now too.  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 ATMEL MCI
Date: Fri, 10 Dec 2010 17:21:04 +0000	[thread overview]
Message-ID: <20101210172104.GA12871@void.printf.net> (raw)
In-Reply-To: <1292004872-5122-1-git-send-email-nicolas.ferre@atmel.com>

Hi Nicolas,

On Fri, Dec 10, 2010 at 07:14:32PM +0100, Nicolas Ferre wrote:
> Based on report made by Yauhen in:
> "MMC: Fix multiblock SDIO transfers in AT91 MCI" patch,
> I report those changes to the brother driver: atmel-mci.
> 
> So, this patch sets SDIO transfer types: SDIO block and SDIO byte
> transfers instead of using ordinary MMC block transfers.
> It is checking opcode for SDIO CMD53 and setting transfer
> type in MCI_CMDR register properly.
> 
> Reported-by: Yauhen Kharuzhy <yauhen.kharuzhy@promwad.com>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> 
> Hi Chris,
> 
> In addition to the at91_mci multiblock SDIO fix, I add this little one too as
> it concerns the brother driver atmel-mci with same issue.
> 
> I hope that you will be able to queue those fixes to .37-final and stable...

That's fine, this is queued now too.  Thanks!

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2010-12-10 17:21 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
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 [this message]
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=20101210172104.GA12871@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.