From: Bjorn Helgaas <bhelgaas@google.com>
To: Tejun Heo <tj@kernel.org>
Cc: Shane Huang <shane.huang@amd.com>,
Jean Delvare <khali@linux-fr.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH v2 3/3] i2c-piix4: add AMD CZ SMBus device ID
Date: Fri, 31 May 2013 13:24:57 -0600 [thread overview]
Message-ID: <CAErSpo4A_tuhsyErPOae5QgBdnUFK4f9kMitH0xUSnV6mYWYrA@mail.gmail.com> (raw)
In-Reply-To: <20130531081623.GB17241@mtj.dyndns.org>
On Fri, May 31, 2013 at 2:16 AM, Tejun Heo <tj@kernel.org> wrote:
> On Fri, May 31, 2013 at 04:12:30PM +0800, Shane Huang wrote:
>> To add AMD CZ SMBus controller device ID.
>>
>> Signed-off-by: Shane Huang <shane.huang@amd.com>
>
> All three patches look good to me.
>
> Reviewed-by: Tejun Heo <tj@kernel.org>
>
> Both 2 and 3 are dependent on the first patch, so it probably would be
> a good idea to route them together (probably w/ stable cc'd). Who
> wants these? Bjorn?
The pci_ids.h change is fine with me. I don't care how they're
routed. If you want me to pick them up, maybe Shane could collect up
the acks & reviewed-bys and add the appropriate stable tags and resend
the series to me.
Bjorn
next prev parent reply other threads:[~2013-05-31 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 8:12 [PATCH v2 3/3] i2c-piix4: add AMD CZ SMBus device ID Shane Huang
2013-05-31 8:16 ` Tejun Heo
2013-05-31 19:24 ` Bjorn Helgaas [this message]
[not found] ` <CAErSpo4A_tuhsyErPOae5QgBdnUFK4f9kMitH0xUSnV6mYWYrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-02 8:02 ` Tejun Heo
[not found] ` <20130602080232.GC8286-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-06-02 8:16 ` Jean Delvare
2013-05-31 8:30 ` 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=CAErSpo4A_tuhsyErPOae5QgBdnUFK4f9kMitH0xUSnV6mYWYrA@mail.gmail.com \
--to=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 \
--cc=tj@kernel.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).