From: mcs6502@gmail.com
To: unlisted-recipients:; (no To-header on input)
Subject: [patch 00/31] pci_ids.h, kernel 2.6.27-rc1, sort DEVICE_IDs within VENDOR_IDs
Date: Wed, 30 Jul 2008 18:50:50 +1000 [thread overview]
Message-ID: <E1KO7OU-0007BT-Ff@wraith.cs.uow.edu.au> (raw)
The following 31 patches attempt to bring pci_ids.h back into order.
patch-01-31: INTEL
patch-02-31: S2IO
patch-03-31: RDC
patch-04-31: ADDIDATA
patch-05-31: MELLANOX
patch-06-31: TIGON3
patch-07-31: TITAN
patch-08-31: SEALEVEL
patch-09-31: SIIG
patch-10-31: ITE
patch-11-31: ENSONIQ
patch-12-31: MARVELL
patch-13-31: SBE
patch-14-31: VIA
patch-15-31: NVIDIA
patch-16-31: CMD/SII
patch-17-31: QLOGIC
patch-18-31: YAMAHA
patch-19-31: MYLEX
patch-20-31: PROMISE
patch-21-31: HP
patch-22-31: SI
patch-23-31: MATROX
patch-24-31: TRIDENT
patch-25-31: AMD
patch-26-31: IBM
patch-27-31: DEC/COMPAQ
patch-28-31: NS
patch-29-31: LSI
patch-30-31: COMPAQ
patch-31-31: ESS
Note 1: I have not attempted a build with these changes. I have done
a sort -u on both the original and fully patched files and there
are only two lines that differ due to padding the ID number to
4 digits.
544c544
< #define PCI_DEVICE_ID_COMPAQ_CISSC 0x46
---
> #define PCI_DEVICE_ID_COMPAQ_CISSC 0x0046
720c720
< #define PCI_DEVICE_ID_IBM_ICOM_FOUR_PORT_MODEL 0x252
---
> #define PCI_DEVICE_ID_IBM_ICOM_FOUR_PORT_MODEL 0x0252
Note 2: I have not made any changes to the ATI section as this appears
to be sorted into chip families.
Note 3: I have not moved the following:
PCI_VENDOR_ID_TOSHIBA_2 (it is adjacent to PCI_VENDOR_ID_TOSHIBA)
PCI_DEVICE_ID_SEGA_BBA (it seems to be missing a PCI_VENDOR_ID_SEGA line)
PCI_VENDOR_ID_ADDIDATA_OLD (it is adjacent to PCI_VENDOR_ID_ADDIDATA)
next reply other threads:[~2008-07-30 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 8:50 mcs6502 [this message]
2008-07-30 10:42 ` Andrew Morton
2008-07-30 10:35 ` Alan Cox
2008-07-30 14:23 ` Jesse Barnes
2008-07-30 15:10 ` Arjan van de Ven
2008-07-30 15:41 ` Jesse Barnes
2008-07-30 12:13 ` Theodore Tso
2008-07-30 13:54 ` David Wilson
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=E1KO7OU-0007BT-Ff@wraith.cs.uow.edu.au \
--to=mcs6502@gmail.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
all inboxes | Powered by JetHome®