From: Tejun Heo <tj@kernel.org>
To: shane.huang@amd.com
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Add AMD SB900 SATA/IDE controller device IDs
Date: Wed, 29 Jul 2009 13:02:03 +0900 [thread overview]
Message-ID: <4A6FC9BB.5010107@kernel.org> (raw)
In-Reply-To: <1248838489.3470.7.camel@zm-desktop>
Shane Huang wrote:
> Update the patch with Tejun's request to add RAID comment.
> === CUT HERE ===
You usually put explanations like above which shouldn't go into commit
message below ---.
> Add AMD SB900 SATA/IDE controller device IDs.
>
> Signed-off-by: Shane Huang <shane.huang@amd.com>
---
Like this.
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2009-07-29 4:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 3:34 [PATCH] Add AMD SB900 SATA/IDE controller device IDs Shane Huang
2009-07-29 4:02 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 6:29 Shane Huang
2009-07-28 7:52 ` Tejun Heo
2009-07-29 0:56 ` Jeff Garzik
2009-07-29 2:32 ` Huang, Shane
2009-07-29 2:42 ` Jeff Garzik
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=4A6FC9BB.5010107@kernel.org \
--to=tj@kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=shane.huang@amd.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;
as well as URLs for NNTP newsgroup(s).