From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
Cc: wux@landicorp.com,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Hamish Guthrie <hamish@prodigi.ch>,
Andrew Victor <andrew@sanpeople.com>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [PATCH] mmc: at91_mci: fix hanging and rework to match flowcharts
Date: Mon, 9 Jul 2007 12:51:25 +0200 [thread overview]
Message-ID: <20070709125125.4d4bc2bc@poseidon.drzeus.cx> (raw)
In-Reply-To: <4688FE50.7050806@drzeus.cx>
On Mon, 02 Jul 2007 15:32:00 +0200
Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> Nicolas Ferre wrote:
> > Fixes hanging using multi block operations (seen during CMD25).
> > Follows closely the datasheet flowcharts.
> >
> > This piece of code handles better big file writing. I had to take
> > care of the notbusy signal during write (at91_mci_handle_cmdrdy
> > function) and to rearrange the AT91_MCI_ENDRX and AT91_MCI_RXBUFF
> > flag usage.
> >
> > Signed-off-by: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
> > ---
>
> Most of the patch looks ok. Do you want to wait for some more tests
> or should I chuck this into the imminent merge window?
>
*ping*
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-07-09 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 12:16 [PATCH] mmc: at91_mci: fix hanging and rework to match flowcharts Nicolas Ferre
2007-07-02 12:45 ` Marc Pignat
2007-07-02 13:32 ` Pierre Ossman
2007-07-09 10:51 ` Pierre Ossman [this message]
2007-07-09 12:48 ` Nicolas Ferre
2007-07-02 19:13 ` Mariusz Kozlowski
2007-07-09 12:58 ` Nicolas Ferre
2007-07-09 16:27 ` Pierre Ossman
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=20070709125125.4d4bc2bc@poseidon.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=andrew@sanpeople.com \
--cc=hamish@prodigi.ch \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@rfo.atmel.com \
--cc=wux@landicorp.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