From: Jaehoon Chung <jh80.chung@samsung.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: "'Doug Anderson'" <dianders@chromium.org>,
"'Jaehoon Chung'" <jh80.chung@samsung.com>,
"'Chris Ball'" <cjb@laptop.org>,
"'Will Newton'" <will.newton@gmail.com>,
"'Bing Zhao'" <bzhao@marvell.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, 20 Jun 2013 10:49:07 +0900 [thread overview]
Message-ID: <51C25F93.9050004@samsung.com> (raw)
In-Reply-To: <001801ce6c20$6ba39900$42eacb00$%jun@samsung.com>
Hi All,
I tested with Seungwon's patch and this patch.
I'm agreed with Seungwon's opinion.
Best Regards,
Jaehoon Chung
On 06/18/2013 09:36 PM, Seungwon Jeon wrote:
> On Thursday, June 13, 2013, Doug Anderson wrote:
>> Seungwon,
>>
>> On Wed, Apr 10, 2013 at 12:02 AM, Seungwon Jeon <tgih.jun@samsung.com> wrote:
>>>>> There are two solutions we have applied.
>>>>
>>>> I'm a little confused. Have you already applied one or both of the
>>>> solutions you list below, or are you proposing them as alternates to
>>>> the patch I submitted?
>>> Yes, first one already has been applied.
>>> I wanted to introduce our fix. Did you try to test with these fixes?
>>
>> I'm coming back to this after being quite distracted for a while.
>>
>> I'm a little confused in that you said that your first fix was already
>> applied. I don't see it anywhere. Did you mean that you've already
>> applied it locally, or that it's applied in some git tree somewhere?
>> If so, can you point me to it?
>>
>> If this hasn't been sent out anywhere, perhaps you could send out
>> official patches?
> Currently, it has just applied for some projects, not official patch.
>>
>> 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.
>
> Thanks,
> Seungwon Jeon
>>
>> -Doug
>
> --
> 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
>
prev parent reply other threads:[~2013-06-20 1:48 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
2013-06-27 18:18 ` Bing Zhao
2013-06-20 1:49 ` Jaehoon Chung [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=51C25F93.9050004@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox