From: Wolfram Sang <wsa@the-dreams.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [RFC PATCH v2 0/2] mmc: core: process ECC errors raised in stop cmds
Date: Mon, 12 Jun 2017 13:29:02 +0200 [thread overview]
Message-ID: <20170612112902.GA1504@katana> (raw)
In-Reply-To: <CAPDyKFqSr+3B5wq7+3+fDhB5etwEGhBadA0X7L9Tu6FUmKJgcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Mon, Jun 12, 2017 at 10:30:27AM +0200, Ulf Hansson wrote:
> On 8 April 2017 at 22:20, Wolfram Sang <wsa+renesas@sang-engineering.com> wrote:
> > Here is the second RFC for handling ECC errors flagged in the stop command
> > after a multiblock transfer. It is still RFC because I could only test it by
> > inducing ECC errors in software (see patch for TMIO below). Shimoda-san, can
> > you try this series with the SD tester again? That would be very kind.
> >
> > Other than that, I hope the patch descriptions and comments explain the single
> > steps. Looking forward for thoughts.
>
> Apologize for the delay!
>
> I looked into these and the changes seems reasonable. I have applied
> them for next to allow them to get some test coverage.
Awesome, thanks Ulf!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-12 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 20:20 [RFC PATCH v2 0/2] mmc: core: process ECC errors raised in stop cmds Wolfram Sang
2017-04-08 20:20 ` [RFC PATCH v2 1/2] mmc: core: check also R1 response for stop commands Wolfram Sang
2017-04-08 20:20 ` [RFC PATCH v2 2/2] mmc: core: for data errors, take response of stop cmd into account Wolfram Sang
2017-06-12 8:30 ` [RFC PATCH v2 0/2] mmc: core: process ECC errors raised in stop cmds Ulf Hansson
2017-06-12 11:29 ` Wolfram Sang [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=20170612112902.GA1504@katana \
--to=wsa@the-dreams.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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