From: Jaehoon Chung <jh80.chung@samsung.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: 'Bing Zhao' <bzhao@marvell.com>,
'Doug Anderson' <dianders@chromium.org>,
'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-kernel@vger.kernel.org
Subject: Re: [PATCH] RFC: mmc: dw_mmc: Always go to STATE_DATA_BUSY from STATE_DATA_ERROR
Date: Thu, 27 Jun 2013 12:36:18 +0900 [thread overview]
Message-ID: <51CBB332.2050903@samsung.com> (raw)
In-Reply-To: <001001ce720f$f96980c0$ec3c8240$%jun@samsung.com>
Hi Seungwon,
I didn't get the same result..In my case, it's working fine.
But as Bing's result, i will check more and share the result.
Best Regards,
Jaehoon Chung
On 06/26/2013 10:53 AM, Seungwon Jeon wrote:
> Hi Jaehoon,
> Do you have the same result?
> Could you share the result?
>
> Thanks,
> Seungwon Jeon
> On Tuesday, June 25 2013, Bing Zhao wrote:
>>> I think the proposal on the table is to take Seungwon's patches
>>> instead of mine. Assuming they solve your problems, I'm OK with that.
>>> I think he was requesting testing the first of his two patches alone
>>> and then both of his two patches together.
>>
>> Test #1: Swungwon's patch #1 alone [1]
>> Test #2: Swungwon's patch #2 alone [1]
>> Test #3: Swungwon's patch #1 and #2 [1]
>> Test #4: Doug's original patch [2]
>>
>> Test #1 and #3: it doesn't work; system reboots due to kernel hung_task
>> Test #2 and #4: it works; instead of hung_task driver gets CRC error (which is expected)
>>
>> Thanks,
>> Bing
>>
>> [1] https://lkml.org/lkml/2013/4/8/316
>> [2] https://lkml.org/lkml/2013/3/15/583
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-06-27 3:36 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
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 [this message]
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=51CBB332.2050903@samsung.com \
--to=jh80.chung@samsung.com \
--cc=asnagarajan@chromium.org \
--cc=bzhao@marvell.com \
--cc=cjb@laptop.org \
--cc=dianders@chromium.org \
--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.