From: kmpark@infradead.org (Kyungmin Park)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s5pc110: SDHCI-s3c can override host capabilities
Date: Fri, 11 Jun 2010 08:06:45 +0900 [thread overview]
Message-ID: <AANLkTinwSxo4OqWlwQE-RxpG8WubLku2-77k2q7DPphr@mail.gmail.com> (raw)
In-Reply-To: <20100610134304.c109811a.akpm@linux-foundation.org>
hi,
On Fri, Jun 11, 2010 at 5:43 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Sat, 05 Jun 2010 11:40:53 +0900
> Kyungmin Park <kmpark@infradead.org> wrote:
>
>> From: Kyungmin Park <kmpark@infradead.org>
>> To: linux-arm-kernel at lists.infradead.org, linux-mmc at vger.kernel.org, akpm at linux-foundation.org, ben-linux at fluff.org
>> Subject: [PATCH] s5pc110: SDHCI-s3c can override host capabilities
>> Date: Sat, 05 Jun 2010 11:40:53 +0900
>> User-Agent: Mutt/1.5.14 (2007-02-12)
>>
>> Each board can override the default sdhci host capabilities.
>> Some board has broken features by hardwares and support 8-bit bandwidth.
>>
>> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>
> The way this patch was presented, it will go into git with an Author:
> address of "kmpark at infradead.org", but a Signed-off-by: address of
> "kyungmin.park at samsung.com". ?Which is a little odd.
>
> The way to prevent that is to put an explicit "From:" line at the top
> of the changelog. ?If that line is absent, people's tools will fall
> back to the From: line in the mail headers, which is what happened
> here.
>
> Please let me know if you want me to make any changes to these three
> patches.
>
No problem, please fix it freely.
Next time, I'll add the From line.
One more, mails from Marek has duplicated patches, so please ignore it.
Thank you,
Kyungmin Park
prev parent reply other threads:[~2010-06-10 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 2:40 [PATCH] s5pc110: SDHCI-s3c can override host capabilities Kyungmin Park
2010-06-10 20:43 ` Andrew Morton
2010-06-10 23:06 ` Kyungmin Park [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=AANLkTinwSxo4OqWlwQE-RxpG8WubLku2-77k2q7DPphr@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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).