From: Xose Vazquez Perez <xose@wanadoo.es>
To: matthartley@yahoo.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] linux-2.4.21-rc5-ac2
Date: Fri, 30 May 2003 18:07:47 +0200 [thread overview]
Message-ID: <3ED781D3.8030408@wanadoo.es> (raw)
Matt Hartley wrote:
>Alan,
>After noticing that drivers/pci/pci.ids was over nine months old, I
>grabbed the latest list off of http://pciids.sourceforge.net, modded it
>to include a few recent submissions and to fix a couple of broken
>lines, and created this patch.
>Let me know if you have any problems with it.
There is not sync between kernel pci.ids and pciids DB since time ago.
Some ids are only in kernel, some ids newer in pciids and some ids are in both
with differents names. It is not so easy like to do a diff.
It's necessary to review every id from diff output _one by one._
But in general, pciids DB is more updated.
regards,
--
Software is like sex, it's better when it's bug free.
next reply other threads:[~2003-05-30 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 16:07 Xose Vazquez Perez [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-30 8:33 [PATCH] linux-2.4.21-rc5-ac2 Matt Hartley
2003-05-30 15:40 ` Alan Cox
2003-06-02 4:10 ` Matt Hartley
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=3ED781D3.8030408@wanadoo.es \
--to=xose@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=matthartley@yahoo.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