From: Doug Anderson <dianders@chromium.org>
To: Bing Zhao <bzhao@marvell.com>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Chris Ball <cjb@laptop.org>, Will Newton <will.newton@gmail.com>,
Ashok Nagarajan <asnagarajan@chromium.org>,
Paul Stewart <pstew@chromium.org>,
Olof Johansson <olof@lixom.net>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RFC: mmc: dw_mmc: Always go to STATE_DATA_BUSY from STATE_DATA_ERROR
Date: Tue, 18 Jun 2013 12:52:37 -0700 [thread overview]
Message-ID: <CAD=FV=Xz-Cp86u=w8m91AEMJgH-o6cLkz6_udVw_3bm7Tm0OiA@mail.gmail.com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430EA2AA2513@SC-VEXCH1.marvell.com>
Bing,
On Tue, Jun 18, 2013 at 12:46 PM, Bing Zhao <bzhao@marvell.com> wrote:
> Hi Seungwon,
>
>> > I don't have the failing unit myself, so we'll have to get Bing to try
>> > the patches. You are suggesting that we try applying both of your
>> > patches, right?
>> Did you test the patch?
>> I wonder that both are good for your side.
>
> I tested Doug's patch on my failing unit.
>
> Without this patch, mmc got hung_task and rebooted eventually.
> With this patch applied, mmc returns CRC error instead of hung_task, and the error is handled gracefully.
Have you tried one or both or Seungwon's fixes without mine?
-Doug
next prev parent reply other threads:[~2013-06-18 19:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 21:29 [PATCH] RFC: mmc: dw_mmc: Always go to STATE_DATA_BUSY from STATE_DATA_ERROR Doug Anderson
2013-03-18 10:21 ` Jaehoon Chung
2013-03-26 18:06 ` Doug Anderson
2013-04-05 8:18 ` Jaehoon Chung
2013-04-08 5:10 ` Jaehoon Chung
2013-04-08 12:17 ` Seungwon Jeon
2013-04-08 23:09 ` Doug Anderson
2013-04-10 7:02 ` Seungwon Jeon
2013-04-10 8:51 ` Jaehoon Chung
2013-06-12 19:06 ` Doug Anderson
2013-06-18 12:36 ` Seungwon Jeon
2013-06-18 19:46 ` Bing Zhao
2013-06-18 19:52 ` Doug Anderson [this message]
2013-06-18 20:01 ` Bing Zhao
2013-06-21 3:33 ` Doug Anderson
2013-06-25 3:54 ` Bing Zhao
2013-06-26 1:53 ` Seungwon Jeon
2013-06-27 3:36 ` Jaehoon Chung
2013-06-27 18:18 ` Bing Zhao
2013-06-20 1:49 ` Jaehoon Chung
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='CAD=FV=Xz-Cp86u=w8m91AEMJgH-o6cLkz6_udVw_3bm7Tm0OiA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=asnagarajan@chromium.org \
--cc=bzhao@marvell.com \
--cc=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pstew@chromium.org \
--cc=tgih.jun@samsung.com \
--cc=will.newton@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.