From: Jaehoon Chung <jh80.chung@samsung.com>
To: Shawn Lin <shawn.lin@rock-chips.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mmc: dw_mmc: remove unused EVENT_XFER_ERROR
Date: Mon, 15 Feb 2016 07:27:11 +0900 [thread overview]
Message-ID: <56C0FF3F.4010706@samsung.com> (raw)
In-Reply-To: <56BDC2A0.1000702@rock-chips.com>
On 02/12/2016 08:31 PM, Shawn Lin wrote:
> On 2016/2/4 14:12, Jaehoon Chung wrote:
>> Hi, Shawn.
>>
>> On 02/03/2016 12:26 PM, Shawn Lin wrote:
>>> EVENT_XFER_ERROR isn't been used now, so we can
>>> remove it.
>>
>> If you are ok, after changing the commit message, I will apply this.
>> Thanks!
>
> Should I respin v2 to amend the commit msg? :-)
Not important..but i want to use this. :)
"we can remove it" -> "It can be removed."
Best Regards,
Jaehoon Chung
>
>>
>> Best Regards,
>> Jaehoon Chung
>>
>>>
>>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>>> ---
>>>
>>> include/linux/mmc/dw_mmc.h | 1 -
>>> 1 file changed, 1 deletion(-)
>>>
>>> diff --git a/include/linux/mmc/dw_mmc.h b/include/linux/mmc/dw_mmc.h
>>> index 89df7ab..b29e06e 100644
>>> --- a/include/linux/mmc/dw_mmc.h
>>> +++ b/include/linux/mmc/dw_mmc.h
>>> @@ -36,7 +36,6 @@ enum {
>>> EVENT_XFER_COMPLETE,
>>> EVENT_DATA_COMPLETE,
>>> EVENT_DATA_ERROR,
>>> - EVENT_XFER_ERROR
>>> };
>>>
>>> struct mmc_data;
>>>
>>
>>
>>
>>
>
>
next prev parent reply other threads:[~2016-02-14 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 3:26 [PATCH 1/2] mmc: dw_mmc: remove unused EVENT_XFER_ERROR Shawn Lin
2016-02-04 6:12 ` Jaehoon Chung
2016-02-12 11:31 ` Shawn Lin
2016-02-14 22:27 ` Jaehoon Chung [this message]
2016-02-14 22:29 ` Jaehoon Chung
2016-02-15 0:20 ` Shawn Lin
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=56C0FF3F.4010706@samsung.com \
--to=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.com \
--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).