From: Jeff Garzik <jgarzik@pobox.com>
To: Kieran Morrissey <linux@mgpenguin.net>
Cc: greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.1: Update PCI Name database, fix gen-devlist.c for long device names.
Date: Wed, 14 Jan 2004 23:05:28 -0500 [thread overview]
Message-ID: <40061188.8060705@pobox.com> (raw)
In-Reply-To: <5.1.0.14.2.20040115140515.00af1318@mail.mgpenguin.net>
Kieran Morrissey wrote:
> Hi all and sundry..
>
> Although /proc/pci and by extension the name database is allegedly
> legacy and therefore deprecated, some (including myself) still use it
> for things such as phpSysInfo, and the still-widespread usage of it is
> obvious in the regularity of slight patches to pci.ids. So, this is an
> all-inclusive patch to bring things up to date:
>
> * Updates pci.ids with a snapshot from http://pciids.sourceforge.net/ as
> at 14 Jan 04.
> * Fixes gen-devlist.c to truncate long device names rather than reject
> the whole database
> (previously the latest databases had some devices that were too long
> and caused a kernel with the latest db to fail to compile)
Well, appreciated, but we really do need to remove it. We don't need
these strings in the kernel at all. pci.ids is just a static lookup
table that is best kept in userspace.
Jeff
next prev parent reply other threads:[~2004-01-15 4:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 3:28 [PATCH] 2.6.1: Update PCI Name database, fix gen-devlist.c for long device names Kieran Morrissey
2004-01-15 4:05 ` Jeff Garzik [this message]
2004-01-15 9:17 ` Ingo Oeser
2004-01-16 1:23 ` Greg KH
2004-01-16 4:25 ` Dave Jones
2004-01-20 1:29 ` Greg KH
2004-01-16 1:24 ` Greg KH
2004-01-17 10:39 ` Martin Mares
2004-01-20 1:30 ` Greg KH
2004-01-20 5:07 ` Kieran Morrissey
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=40061188.8060705@pobox.com \
--to=jgarzik@pobox.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@mgpenguin.net \
/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