From: Tejun Heo <tj@kernel.org>
To: Shane Huang <shane.huang@amd.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Jean Delvare <khali@linux-fr.org>,
linux-pci@vger.kernel.org, linux-ide@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 1/3] pci_ids: put Hudson-2 device IDs together
Date: Fri, 31 May 2013 12:33:55 +0900 [thread overview]
Message-ID: <20130531033355.GA31965@mtj.dyndns.org> (raw)
In-Reply-To: <1369999039-1983-1-git-send-email-shane.huang@amd.com>
On Fri, May 31, 2013 at 07:17:19PM +0800, Shane Huang wrote:
> To put all AMD Hudson-2 device IDs together for better maintenance.
>
> Signed-off-by: Shane Huang <shane.huang@amd.com>
Bjorn, how should we route these patches? The second will conflict
with the first. If it's okay, I can take the first two through libata
tree.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-05-31 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 11:17 [PATCH 1/3] pci_ids: put Hudson-2 device IDs together Shane Huang
2013-05-31 3:33 ` Tejun Heo [this message]
2013-05-31 6:05 ` Jean Delvare
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=20130531033355.GA31965@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=bhelgaas@google.com \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@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).