From: Pierre Ossman <pierre@ossman.eu>
To: "Wolfgang Mües" <wolfgang.mues@auerswald.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Matt Fleming" <matt@console-pimps.org>,
"David Brownell" <dbrownell@users.sourceforge.net>,
"Mike Frysinger" <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc_spi: do propper retry managment in the block layer
Date: Wed, 13 May 2009 21:45:51 +0200 [thread overview]
Message-ID: <20090513214551.739757fd@mjolnir.ossman.eu> (raw)
In-Reply-To: <200905061145.30698.wolfgang.mues@auerswald.de>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Wed, 6 May 2009 11:45:30 +0200
Wolfgang Mües <wolfgang.mues@auerswald.de> wrote:
>
> I checked the drivers sourcecode and found that most drivers are using EINVAL
> for non-recoverable parameter errors.
>
> The only driver which uses EINVAL for errors which might result from
> transmission failures is mmc_spi.
>
> So I think it would be OK to use another error code in mmc_spi for these
> cases:
>
> * EILSEQ Basic format problem with the received or sent data
> * (e.g. CRC check failed, incorrect opcode in response
> * or bad end bit)
>
> Would you accept a patch to report another error code in mmc_spi?
>
EILSEQ seems correct for SPI bit errors, so I'd gladly accept such a
patch, yes. :)
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-05-13 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 9:55 Wolfgang Mües
2009-04-10 22:10 ` Pierre Ossman
2009-04-14 14:27 ` Wolfgang Mües
2009-04-28 19:57 ` Pierre Ossman
2009-05-06 9:45 ` Wolfgang Mües
2009-05-13 19:45 ` Pierre Ossman [this message]
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=20090513214551.739757fd@mjolnir.ossman.eu \
--to=pierre@ossman.eu \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--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
all inboxes | Powered by JetHome®