From: Greg KH <greg@kroah.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Greg KH <gregkh@suse.de>, Jason Gaston <jason.d.gaston@intel.com>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
i2c@lm-sensors.nu
Subject: Re: [PATCH 2.6.24] pci_ids: patch for Intel ICH10 DeviceID's
Date: Tue, 12 Feb 2008 07:26:42 -0800 [thread overview]
Message-ID: <20080212152642.GA19441@kroah.com> (raw)
In-Reply-To: <20080212100338.21c0adf5@hyperion.delvare>
On Tue, Feb 12, 2008 at 10:03:38AM +0100, Jean Delvare wrote:
> On Mon, 28 Jan 2008 17:20:36 -0800, Jason Gaston wrote:
> > This patch adds the Intel ICH10 LPC and SMBus Controller DeviceID's.
> >
> > Signed-off-by: Jason Gaston <jason.d.gaston@intel.com>
> >
> > --- linux-2.6.24/include/linux/pci_ids.h.orig 2008-01-24 14:58:37.000000000 -0800
> > +++ linux-2.6.24/include/linux/pci_ids.h 2008-01-28 15:05:41.000000000 -0800
> > @@ -2339,6 +2339,12 @@
> > #define PCI_DEVICE_ID_INTEL_MCH_PC1 0x359a
> > #define PCI_DEVICE_ID_INTEL_E7525_MCH 0x359e
> > #define PCI_DEVICE_ID_INTEL_IOAT_CNB 0x360b
> > +#define PCI_DEVICE_ID_INTEL_ICH10_0 0x3a14
> > +#define PCI_DEVICE_ID_INTEL_ICH10_1 0x3a16
> > +#define PCI_DEVICE_ID_INTEL_ICH10_2 0x3a18
> > +#define PCI_DEVICE_ID_INTEL_ICH10_3 0x3a1a
> > +#define PCI_DEVICE_ID_INTEL_ICH10_4 0x3a30
> > +#define PCI_DEVICE_ID_INTEL_ICH10_5 0x3a60
> > #define PCI_DEVICE_ID_INTEL_IOAT_SNB 0x402f
> > #define PCI_DEVICE_ID_INTEL_IOAT_SCNB 0x65ff
> > #define PCI_DEVICE_ID_INTEL_TOLAPAI_0 0x5031
>
> Greg, please pick this patch quickly so that it makes it to -mm and the
> other patches that depend on it can be pushed there as well.
Will do, give me a few hours...
thanks,
greg k-h
prev parent reply other threads:[~2008-02-12 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 1:20 [PATCH 2.6.24] pci_ids: patch for Intel ICH10 DeviceID's Jason Gaston
2008-01-29 0:21 ` Grant Grundler
2008-01-29 0:37 ` Gaston, Jason D
2008-02-12 9:03 ` Jean Delvare
2008-02-12 15:26 ` Greg KH [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=20080212152642.GA19441@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=i2c@lm-sensors.nu \
--cc=jason.d.gaston@intel.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.