From: Greg KH <gregkh@suse.de>
To: Grant <lkml@dodo.com.au>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Grant Coady <grant_lkml@dodo.com.au>, Greg KH <greg@kroah.com>,
"Gaston, Jason D" <jason.d.gaston@intel.com>,
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: Tue, 13 Sep 2005 00:03:24 -0700 [thread overview]
Message-ID: <20050913070324.GA7968@suse.de> (raw)
In-Reply-To: <kctci1lqlgbr9ct7as48j551o6v9013504@4ax.com>
On Tue, Sep 13, 2005 at 04:46:45PM +1000, Grant wrote:
> On Sun, 11 Sep 2005 04:51:10 -0400, Jeff Garzik <jgarzik@pobox.com> wrote:
> >
> >pci_ids.h should be the place where PCI IDs (class, vendor, device) are
> >collected.
>
> Few files reference it.
include/pci.h does, so pretty much every pci driver does because of
that.
> >Long term, we should be able to trim a lot of device ids, since they are
> >usually only used in one place.
>
> Well, they're not, and trimming a file marked for removal is pointless.
Huh? That file isn't marked for removal, that was the id database,
which is now gone...
thanks,
greg k-h
next prev parent reply other threads:[~2005-09-13 7:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 21:55 [PATCH 2.6.13-rc4 1/1] pci_ids: patch for Intel ICH7R 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-07-29 16:24 Jason Gaston
2005-07-29 21:49 ` 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=20050913070324.GA7968@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=grant_lkml@dodo.com.au \
--cc=greg@kroah.com \
--cc=jason.d.gaston@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dodo.com.au \
--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