From: Phil Oester <kernel@linuxace.com>
To: David Fox <david.fox@linspire.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc2 pci_ids.h cleanup is a pain
Date: Mon, 21 Nov 2005 14:31:04 -0800 [thread overview]
Message-ID: <20051121223104.GA6881@linuxace.com> (raw)
In-Reply-To: <438249CB.8050200@linspire.com>
On Mon, Nov 21, 2005 at 02:27:23PM -0800, David Fox wrote:
> I'm sure I'm not the only person that applies patches to the kernel that
> use some of the 500 plus PCI IDS eliminated from pci_ids.h by rc2. I
> would like to see the PCI ids that were removed simply because the don't
> occur in the main kernel source restored. Is there a rationale for
> removing them that I'm not aware of?
As long as you are patching the kernel, is there some reason you can't
add back the PCI IDs you require?
Phil
next prev parent reply other threads:[~2005-11-21 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:27 2.6.15-rc2 pci_ids.h cleanup is a pain David Fox
2005-11-21 22:31 ` Phil Oester [this message]
2005-11-21 22:44 ` Greg KH
2005-11-23 0:25 ` Andrew Morton
2005-11-23 1:51 ` Grant Coady
2005-11-23 2:12 ` Andrew Morton
2005-11-23 4:19 ` Dave Jones
2005-11-23 7:55 ` Grant Coady
2005-11-23 21:41 ` Grant Coady
2005-11-24 4:00 ` Dave Jones
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=20051121223104.GA6881@linuxace.com \
--to=kernel@linuxace.com \
--cc=david.fox@linspire.com \
--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