From: Shawn Lin <shawn.lin@rock-chips.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: shawn.lin@rock-chips.com, Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: dw_mmc: remove repetitive clear interrupt
Date: Tue, 26 Jan 2016 08:40:40 +0800 [thread overview]
Message-ID: <56A6C088.8060103@rock-chips.com> (raw)
In-Reply-To: <1630713.rPyRx6D05H@wuerfel>
On 2016/1/25 16:55, Arnd Bergmann wrote:
> On Monday 25 January 2016 12:56:25 Shawn Lin wrote:
>> On 2016/1/25 12:14, Jaehoon Chung wrote:
>>> Hi, Shawn.
>>>
>>> On 01/25/2016 10:13 AM, Shawn Lin wrote:
>>>> This patch remove repetitive clear interrupt while
>>>> probing dw_mmc.
>>>
>>> Could you explain to me more?
>>
>> yes, it's a trivial improvement.
>>
>> dw_mci_probe clear interrupt and disable all interrupt firstly.
>> Then commit 2da1d7f2 add a new clear-interrupt operation before
>> enable some interrupt. I can't see any reason to clear it twice
>> here. No any side effect I had found in my test pattern without this
>> . May I miss some important case?
>>
>
> The explanation should go into the patch description to explain why
> it is done. The one sentence "This patch remove repetitive clear
> interrupt while probing dw_mmc" that you wrote instead can be
> removed, it just repeats the patch subject.
>
Hi Arnd
Thanks for sharing that. I will respin v2 to add this into commit-msg.
> Arnd
>
>
>
--
Best Regards
Shawn Lin
prev parent reply other threads:[~2016-01-26 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 1:13 [PATCH] mmc: dw_mmc: remove repetitive clear interrupt Shawn Lin
2016-01-25 4:14 ` Jaehoon Chung
2016-01-25 4:56 ` Shawn Lin
2016-01-25 8:55 ` Arnd Bergmann
2016-01-26 0:40 ` Shawn Lin [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=56A6C088.8060103@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=arnd@arndb.de \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).