From: Jeff Garzik <jgarzik@pobox.com>
To: Jason Gaston <jason.d.gaston@intel.com>
Cc: mj@ucw.cz, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.13-rc4 1/1] pci_ids: patch for Intel ICH7R
Date: Fri, 29 Jul 2005 17:49:12 -0400 [thread overview]
Message-ID: <42EAA458.2010004@pobox.com> (raw)
In-Reply-To: <200507290924.40952.jason.d.gaston@intel.com>
Jason Gaston wrote:
> Hello,
>
> This patch adds the Intel ICH7R SATA RAID DID to the pci_ids.h file. This patch was built against the 2.6.13-rc4 kernel.
> If acceptable, please apply.
>
> Thanks,
>
> Jason Gaston
>
> Signed-off-by: Jason Gaston <Jason.d.gaston@intel.com>
>
> --- linux-2.6.13-rc4/include/linux/pci_ids.h.orig 2005-07-29 09:06:03.841520568 -0700
> +++ linux-2.6.13-rc4/include/linux/pci_ids.h 2005-07-29 09:06:42.256680576 -0700
> @@ -2454,6 +2454,7 @@
> #define PCI_DEVICE_ID_INTEL_ICH7_3 0x27c1
> #define PCI_DEVICE_ID_INTEL_ICH7_30 0x27b0
> #define PCI_DEVICE_ID_INTEL_ICH7_31 0x27bd
> +#define PCI_DEVICE_ID_INTEL_ICH7_4 0x27c3
> #define PCI_DEVICE_ID_INTEL_ICH7_5 0x27c4
> #define PCI_DEVICE_ID_INTEL_ICH7_6 0x27c5
> #define PCI_DEVICE_ID_INTEL_ICH7_7 0x27c8
Where is this actually used?
I purposefully do not use PCI_DEVICE_ID_xxx in my drivers, because I
feel that linux/pci_ids.h is constantly patched for little value.
Device ids, unlike vendor ids, are largely single-use constants.
Jeff
next prev parent reply other threads:[~2005-07-29 21:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 16:24 [PATCH 2.6.13-rc4 1/1] pci_ids: patch for Intel ICH7R Jason Gaston
2005-07-29 21:49 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-29 21:55 Gaston, Jason D
2005-07-29 22:21 ` Jeff Garzik
2005-07-29 22:26 ` Andrew Morton
2005-07-29 22:29 ` Jeff Garzik
2005-07-30 2:28 ` Grant Coady
2005-07-30 3:52 ` Jeff Garzik
2005-07-30 4:54 ` Grant Coady
2005-08-11 19:22 ` Jeff Garzik
2005-09-11 3:11 ` Greg KH
2005-09-11 8:00 ` Grant Coady
2005-09-11 8:51 ` Jeff Garzik
2005-09-11 20:40 ` Grant Coady
2005-09-13 6:46 ` Grant
2005-09-13 7:03 ` Greg KH
2005-09-13 8:14 ` Grant Coady
2005-11-02 5:38 ` Grant Coady
2005-07-30 9:42 ` Grant Coady
2005-08-11 19:23 ` Jeff Garzik
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=42EAA458.2010004@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=jason.d.gaston@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox