From: Paul Fulghum <paulkf@microgate.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "torvalds@transmeta.com" <torvalds@transmeta.com>
Subject: [PATCH] pci.ids 2.5.68 (and question)
Date: 02 May 2003 10:37:27 -0500 [thread overview]
Message-ID: <1051889846.1718.9.camel@diemos> (raw)
This patch adds new PCI IDs to the drivers/pci/pci.ids file.
I've also submitted a (different) patch to pci-ids@ucw.cz
I noticed that the kernel 2.5.68 pci.ids file is significantly
out of date with the latest at pciids.sourceforge.net
so I generated this patch for the current kernel.
Is this the correct thing to do, or should I just wait for
the pciids.sourceforge.net copy to eventually trickle
into the latest kernel source?
--- linux-2.5.68/drivers/pci/pci.ids 2003-04-07 12:31:24.000000000 -0500
+++ linux-2.5.68-mg/drivers/pci/pci.ids 2003-05-01 15:41:38.000000000 -0500
@@ -4815,7 +4815,10 @@
13be Miroku Jyoho Service Co. Ltd
13bf Sharewave Inc
13c0 Microgate Corporation
- 0010 SyncLink WAN Adapter
+ 0010 SyncLink Adapter v1
+ 0020 SyncLink SCC Adapter
+ 0030 SyncLink Multiport Adapter
+ 0210 SyncLink Adapter v2
13c1 3ware Inc
1000 3ware ATA-RAID
1001 3ware 7000-series ATA-RAID
--
Paul Fulghum, paulkf@microgate.com
Microgate Corporation, http://www.microgate.com
reply other threads:[~2003-05-02 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1051889846.1718.9.camel@diemos \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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®