public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Grant Coady <grant_lkml@dodo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] pci_ids.h: cleanup: whitespace and remove unused entries
Date: Mon, 26 Sep 2005 14:35:57 -0700	[thread overview]
Message-ID: <20050926213557.GA21973@kroah.com> (raw)
In-Reply-To: <937ti1hpvcjdk8hf894h651s81nu6il239@4ax.com>

On Mon, Sep 19, 2005 at 09:22:36PM +1000, Grant Coady wrote:
> Greetings,
> 
> This patch cleans up pci_ids.h, reducing size of the file from 
> 104448 to 73438 bytes.  Due to the scripted changes and the 
> requirement to maintain ordering within the file I had to reformat 
> whitespace.
> 
> Compile tested with 'make allmodconfig' with some stuff turned 
> off to get a compile completion.  No missing PCI_* symbols.
> 
> Next step is to fix PCI_* defines distributed in the source, also 
> this file is meant to be included via 'pci.h' some files may need a 
> reference to pci_ids.h removed.  
> 
> As attachment as patch is 92k.

I don't think you need the change to the comments at the top of the
file.

Also, I thought we wanted to keep all of the pci class ids, why did you
delete them?  We should start by removing the pci device and vendor ids
that are not currently used by the kernel, and then slowly move those
ids into the individual drivers, starting with the device ids, and maybe
eventually moving to the vendor ids.

Sound ok?

thanks,

greg k-h

  reply	other threads:[~2005-09-27  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 11:22 [RFC PATCH] pci_ids.h: cleanup: whitespace and remove unused entries Grant Coady
2005-09-26 21:35 ` Greg KH [this message]
2005-09-27  8:32   ` Grant Coady
2005-09-27  8:36     ` Greg KH
2005-09-27 21:23   ` Jeff Garzik
2005-09-27 22:04     ` Grant Coady

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=20050926213557.GA21973@kroah.com \
    --to=greg@kroah.com \
    --cc=grant_lkml@dodo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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