From: Alex Dubov <oakad@yahoo.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>,
David Brownell <david-b@pacbell.net>,
Andrew Victor <linux@maxim.org.za>, Pavel Pisa <ppisa@pikron.com>,
Carlos Aguiar <carlos.aguiar@indt.org.br>,
Anderson Briglia <briglia.anderson@gmail.com>,
"Syed Mohammed, Khasim" <x0khasim@ti.com>,
Russell King <rmk@arm.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] MMC multiwrite capability removal
Date: Sat, 19 Apr 2008 19:34:12 -0700 (PDT) [thread overview]
Message-ID: <896748.37554.qm@web36708.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080419095136.15a50cc9@mjolnir.drzeus.cx>
--- Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> Hi everyone,
>
> I've been planning to remove the MMC multiwrite capability (making it
> always on), but I need some help from all you driver maintainers first.
>
> Ages ago, I had a chat with Axboe about the current situation and it
> turns out that the MMC layer is a bit over-cautious. There are plenty
> of other block devices that cannot report anything more than
> success/failure for the whole request. So it's silly that we're
> crippling the MMC layer when upper layers have to deal with that
> scenario anyway.
>
> What I need from you is and audit of your respective driver(s) and
> check that they do not overestimate the number of successfully written
> blocks. Please send a short reply even if your driver needs no changes.
>
tifm_sd relies on controller to report the number of successfully transferred
blocks. Of course, I cannot be sure to what extent the controller is
trustworthy. It worked fine until now, though.
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
next prev parent reply other threads:[~2008-04-20 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 7:51 [RFC] MMC multiwrite capability removal Pierre Ossman
2008-04-20 2:34 ` Alex Dubov [this message]
2008-04-20 8:30 ` Pierre Ossman
2008-04-20 14:54 ` Alex Dubov
2008-04-21 19:05 ` David Brownell
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=896748.37554.qm@web36708.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=briglia.anderson@gmail.com \
--cc=carlos.aguiar@indt.org.br \
--cc=david-b@pacbell.net \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=ppisa@pikron.com \
--cc=rmk@arm.linux.org.uk \
--cc=x0khasim@ti.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