From: Matt Fleming <matt@console-pimps.org>
To: "Wolfgang Mües" <wolfgang.mues@auerswald.de>
Cc: Pierre Ossman <pierre@ossman.eu>,
David Brownell <david-b@pacbell.net>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Frysinger <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc_spi: use EILSEQ for possible transmission errors
Date: Wed, 10 Jun 2009 08:37:49 +0100 [thread overview]
Message-ID: <20090610073749.GA444@console-pimps.org> (raw)
In-Reply-To: <200906100929.49553.wolfgang.mues@auerswald.de>
On Wed, Jun 10, 2009 at 09:29:49AM +0200, Wolfgang Mües wrote:
>
> From: Wolfgang Muees <wolfgang.mues@auerswald.de>
>
> o This patch changes the reported error code for the responses
> to a command from EINVAL to EFAULT/ENOSYS, as EINVAL is reserved
> for non-recoverable host errors, and the responses from
> the SD/MMC card may be because of recoverable transmission
> errors in the command or in the response. Response codes
> in SPI mode are NOT protected by a checksum, so don't trust them.
>
> This is a revised, minimal-invasive patch version. As Pierre Ossman
> pointed out, EINVAL should only be used for non-recoverable errors
> (and is used so in the whole rest of the mmc framework).
>
> I have checked every instance of EINVAL in the mmc framework - no
> changes were needed here.
>
> This patch is neccessary for doing a sensible retry managment in the
> mmmc block layer (patch will follow).
>
> Signed-off-by: Wolfgang Muees <wolfgang.mues@auerswald.de>
Nice patch Wolfgang and well done for sticking this out ;-)
FWIW,
Acked-by: Matt Fleming <matt@console-pimps.org>
next prev parent reply other threads:[~2009-06-10 7:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 11:24 [PATCH] mmc_spi: use EILSEQ for possible transmission errors Wolfgang Mües
2009-05-19 11:29 ` Matt Fleming
2009-05-19 11:47 ` Wolfgang Mües
2009-05-20 7:53 ` Matt Fleming
2009-05-20 4:49 ` David Brownell
2009-05-20 8:35 ` Wolfgang Mües
2009-05-20 9:20 ` David Brownell
2009-05-20 10:08 ` Pierre Ossman
2009-05-21 2:02 ` David Brownell
2009-05-25 9:04 ` Wolfgang Mües
2009-05-25 9:43 ` David Brownell
2009-05-25 10:18 ` Wolfgang Mües
2009-05-25 11:50 ` Pierre Ossman
2009-05-25 14:59 ` Wolfgang Mües
2009-06-09 18:07 ` Pierre Ossman
2009-06-10 7:29 ` Wolfgang Mües
2009-06-10 7:37 ` Matt Fleming [this message]
2009-06-13 10:57 ` Pierre Ossman
2009-05-25 11:48 ` Pierre Ossman
2009-05-20 10:31 ` Wolfgang Mües
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=20090610073749.GA444@console-pimps.org \
--to=matt@console-pimps.org \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre@ossman.eu \
--cc=vapier.adi@gmail.com \
--cc=wolfgang.mues@auerswald.de \
/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