public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"Jan Klötzke" <jan.kloetzke@technisat.de>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Simon Horman" <horms@verge.net.au>,
	"Masaharu Hayakawa" <masaharu.hayakawa.ry@renesas.com>,
	"KOUEI ABE" <kouei.abe.cp@renesas.com>,
	"DUNG NGUYEN" <dung.nguyen.aj@renesas.com>
Subject: Re: [RFT] mmc: tmio: fix CMD12 (STOP) handling
Date: Thu, 6 Jul 2017 08:38:43 +0200	[thread overview]
Message-ID: <20170706063843.GC1418@katana> (raw)
In-Reply-To: <TY1PR06MB0992844258B8EE4C70C403D2D8D40@TY1PR06MB0992.apcprd06.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]


> I and Dung-san are testing this patch.
> However, this original code doesn't run by our test cases.
> Do you know how this original code runs?
> Anyway, we will try to make a test case somehow now.

Thank you very much, Shimoda-san. I got it tested because a card needed
re-tuning during a transfer.

It might work if you manually induce an error bit in the driver
somewhere. I'll try to find a good sport later, too. However, I am away
from my boards today and tomorrow.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-07-06  6:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 19:28 [RFT] mmc: tmio: fix CMD12 (STOP) handling Wolfram Sang
2017-07-04  9:13 ` Jan.Kloetzke
2017-07-04 13:21 ` Geert Uytterhoeven
2017-07-05 11:19 ` Yoshihiro Shimoda
2017-07-06  6:38   ` Wolfram Sang [this message]
2017-07-07  1:20     ` Yoshihiro Shimoda
2017-07-07  6:43       ` Wolfram Sang
2017-07-11 14:43 ` Ulf Hansson
2017-07-11 15:00   ` Wolfram Sang

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=20170706063843.GC1418@katana \
    --to=wsa@the-dreams.de \
    --cc=dung.nguyen.aj@renesas.com \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=jan.kloetzke@technisat.de \
    --cc=kouei.abe.cp@renesas.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=masaharu.hayakawa.ry@renesas.com \
    --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