From: Chris Ball <cjb@laptop.org>
To: Andrei Warkentin <andreiw@motorola.com>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-mmc@vger.kernel.org
Subject: Re: [comments] MMC: Reliable write support.
Date: Thu, 31 Mar 2011 16:58:07 -0400 [thread overview]
Message-ID: <m3r59nt3c0.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <AANLkTimQgeenQNzPK5oFNPj-dGygdJY1S8gXZWdKAZUU@mail.gmail.com> (Andrei Warkentin's message of "Thu, 31 Mar 2011 15:39:39 -0500")
Hi,
On Thu, Mar 31 2011, Andrei Warkentin wrote:
> I took a look at mmc_test. It seems like it was meant more to test
> cards, rather than block.c functionality, as it issues all MMC
> requests by itself, instead of submitting via block layer. It would be
> separately an interesting an idea to implement an MMC reliable write
> test to mmc_test, but it wouldn't help much with bugs in block.c.
> What do you think?
Ah, that's right. I guess this is just calling for a userspace test
suite, and there's nothing more to be done in the kernel..
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-03-31 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 21:22 Reliable write support Andrei Warkentin
2011-03-24 21:22 ` [comments] MMC: " Andrei Warkentin
2011-03-25 15:14 ` Arnd Bergmann
2011-03-26 7:17 ` Andrei Warkentin
2011-03-26 7:22 ` Andrei Warkentin
2011-03-29 0:50 ` Andrei Warkentin
2011-03-29 7:01 ` Arnd Bergmann
2011-03-29 22:44 ` Andrei Warkentin
2011-03-30 12:05 ` Arnd Bergmann
2011-03-30 22:38 ` Chris Ball
2011-03-31 20:39 ` Andrei Warkentin
2011-03-31 20:58 ` Chris Ball [this message]
2011-03-31 23:40 ` [PATCH] " Andrei Warkentin
2011-04-01 0:47 ` Chris Ball
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=m3r59nt3c0.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=andreiw@motorola.com \
--cc=arnd@arndb.de \
--cc=linux-mmc@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