From: Andrew Morton <akpm@osdl.org>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: rmk+lkml@arm.linux.org.uk, Pierre Ossman <drzeus-list@drzeus.cx>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MMC] Multi sector write transfers
Date: Tue, 3 Oct 2006 15:10:34 -0700 [thread overview]
Message-ID: <20061003151034.a7894df8.akpm@osdl.org> (raw)
In-Reply-To: <20061001124257.17012.78166.stgit@poseidon.drzeus.cx>
Russell is moving away from mmc maintainership so we'll need to do
something different here.
The patches look good to my untrained eye, except...
On Sun, 01 Oct 2006 14:42:57 +0200
Pierre Ossman <drzeus@drzeus.cx> wrote:
> SD cards extend the protocol by allowing the host to query a card how many
> blocks were successfully stored on the medium. This allows us to safely write
> chunks of blocks at once.
I recall Russell nacked multisector mmc-writing when it came up six or
twelve months ago. I don't recall the exact details - lack of trust in
manufacturers supporting it correctly?
Is that concern relevant to this patch?
next prev parent reply other threads:[~2006-10-03 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 12:42 Pierre Ossman
2006-10-03 22:10 ` Andrew Morton [this message]
2006-10-05 6:42 ` 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=20061003151034.a7894df8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=drzeus-list@drzeus.cx \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®