From: Andrew Morton <akpm@linux-foundation.org>
To: Jason Gaston <jason.d.gaston@intel.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz, stable@kernel.org
Subject: Re: [PATCH 2.6.22-rc2] pci_ids: update patch for Intel ICH9M
Date: Tue, 29 May 2007 15:25:45 -0700 [thread overview]
Message-ID: <20070529152545.887fda6c.akpm@linux-foundation.org> (raw)
In-Reply-To: <200705251203.31985.jason.d.gaston@intel.com>
On Fri, 25 May 2007 12:03:31 -0700
Jason Gaston <jason.d.gaston@intel.com> wrote:
> This patch updates the Intel ICH9M LPC Controller DID's, due to a
> specification change.
>
> Signed-off-by: __Jason Gaston <jason.d.gaston@intel.com>
>
> --- linux-2.6.22-rc2/include/linux/pci_ids.h.orig 2007-05-25
> 11:42:11.000000000 -0700
> +++ linux-2.6.22-rc2/include/linux/pci_ids.h 2007-05-25 11:43:28.000000000
> -0700
> @@ -2266,11 +2266,11 @@
> #define PCI_DEVICE_ID_INTEL_ICH8_5 0x283e
> #define PCI_DEVICE_ID_INTEL_ICH8_6 0x2850
> #define PCI_DEVICE_ID_INTEL_ICH9_0 0x2910
> -#define PCI_DEVICE_ID_INTEL_ICH9_1 0x2911
> +#define PCI_DEVICE_ID_INTEL_ICH9_1 0x2917
> #define PCI_DEVICE_ID_INTEL_ICH9_2 0x2912
> #define PCI_DEVICE_ID_INTEL_ICH9_3 0x2913
> #define PCI_DEVICE_ID_INTEL_ICH9_4 0x2914
> -#define PCI_DEVICE_ID_INTEL_ICH9_5 0x2915
> +#define PCI_DEVICE_ID_INTEL_ICH9_5 0x2919
> #define PCI_DEVICE_ID_INTEL_ICH9_6 0x2930
> #define PCI_DEVICE_ID_INTEL_82855PM_HB 0x3340
> #define PCI_DEVICE_ID_INTEL_82830_HB 0x3575
I assume we'll need this in 2.6.21.x as well, otherwise those devices just
won't work when someone tries to run this kernel on them?
next prev parent reply other threads:[~2007-05-29 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 19:03 Jason Gaston
2007-05-29 22:25 ` Andrew Morton [this message]
2007-05-29 22:41 ` Gaston, Jason D
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=20070529152545.887fda6c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jason.d.gaston@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=stable@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
Powered by JetHome