From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Seth Heasley <seth.heasley@intel.com>
Cc: i2c@lm-sensors.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, khali@linux-fr.org
Subject: Re: [PATCH 2.6.26.2] pci_ids: patch for Intel Ibex Peak DeviceIDs
Date: Mon, 11 Aug 2008 10:18:43 -0700 [thread overview]
Message-ID: <200808111018.44024.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200808081616.08158.seth.heasley@intel.com>
On Friday, August 8, 2008 4:16 pm Seth Heasley wrote:
> This patch adds the Intel Ibex Peak (PCH) LPC and SMBus Controller
> DeviceIDs.
>
> Signed-off-by: Seth Heasley <seth.heasley@intel.com>
>
> --- linux-2.6.26.2/include/linux/pci_ids.h.orig 2008-08-08
> 11:07:41.000000000 -0700 +++ linux-2.6.26.2/include/linux/pci_ids.h
> 2008-08-08 11:22:31.000000000 -0700 @@ -2385,6 +2385,9 @@
> #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_PCH_0 0x3b10
> +#define PCI_DEVICE_ID_INTEL_PCH_1 0x3b11
> +#define PCI_DEVICE_ID_INTEL_PCH_2 0x3b30
> #define PCI_DEVICE_ID_INTEL_IOAT_SNB 0x402f
> #define PCI_DEVICE_ID_INTEL_5400_ERR 0x4030
> #define PCI_DEVICE_ID_INTEL_5400_FBD0 0x4035
Should PCH_2 also be added to arch/x86/pci/irq.c? You may as well combine the
irq.c and pci_ids.h patches into one patch too. Care to respin against my
for-linus branch and resubmit?
Thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2008-08-11 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 23:16 [PATCH 2.6.26.2] pci_ids: patch for Intel Ibex Peak DeviceIDs Seth Heasley
2008-08-09 14:00 ` Jean Delvare
2008-08-11 17:18 ` Jesse Barnes [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=200808111018.44024.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seth.heasley@intel.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