public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: lkml@dodo.com.au
Cc: "Gaston, Jason D" <jason.d.gaston@intel.com>,
	mj@ucw.cz, akpm@osdl.org, linux-kernel@vger.kernel.org,
	Greg KH <gregkh@suse.de>
Subject: Re: [PATCH 2.6.13-rc4 1/1] pci_ids: patch for Intel ICH7R
Date: Fri, 29 Jul 2005 23:52:39 -0400	[thread overview]
Message-ID: <42EAF987.7020607@pobox.com> (raw)
In-Reply-To: <n4ple1haga8eano2vt2ipl17mrrmmi36jr@4ax.com>

Grant Coady wrote:
> On Fri, 29 Jul 2005 18:21:05 -0400, Jeff Garzik <jgarzik@pobox.com> wrote:
> 
>>[speaking to the audience]  I wouldn't mind if someone did a pass 
>>through pci_ids.h and removed all the constants that are not being used. 
> 
> 
> Only these seem not referenced by source:
> PCI_CLASS_SYSTEM_PCI_HOTPLUG
> PCI_DEVICE_ID_CYRIX_PCI_MASTER
> PCI_DEVICE_ID_HP_PCI_LBA
> PCI_DEVICE_ID_NP_PCI_FDDI
> PCI_DEVICE_ID_UPCI_RM3_4PORT
> PCI_DEVICE_ID_UPCI_RM3_8PORT
> 
> Source macros refer to:
>   BROOKTREE	sound/pci/bt87x.c
>   YAMAHA	sound/oss/ymfpci.c
> 
> 6 from 2329 entries hardly worth it?

However you did your search, you did it wrong.  The very first two 
entries I tried had zero uses:

[jgarzik@pretzel linux-2.6]$ grepsrc ICH7_22
./include/linux/pci_ids.h:#define PCI_DEVICE_ID_INTEL_ICH7_22   0x27e0
[jgarzik@pretzel linux-2.6]$ grepsrc ICH7_23
./include/linux/pci_ids.h:#define PCI_DEVICE_ID_INTEL_ICH7_23   0x27e2
[jgarzik@pretzel linux-2.6]$


  reply	other threads:[~2005-07-30  3:53 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 [this message]
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
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=42EAF987.7020607@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=jason.d.gaston@intel.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