From: Greg KH <greg@kroah.com>
To: Dave Airlie <airlied@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.20-rc5] intel_rng: substitue magic PCI IDs with macros
Date: Sun, 14 Jan 2007 16:29:24 -0800 [thread overview]
Message-ID: <20070115002924.GA20993@kroah.com> (raw)
In-Reply-To: <20070114230718.GB3874@Ahmed>
On Mon, Jan 15, 2007 at 01:07:18AM +0200, Ahmed S. Darwish wrote:
> On Mon, Jan 15, 2007 at 06:31:01AM +1100, Dave Airlie wrote:
> > On 1/15/07, Arjan van de Ven <arjan@infradead.org> wrote:
> > >On Sun, 2007-01-14 at 19:24 +0200, Ahmed S. Darwish wrote:
> > >> Substitue intel_rng magic PCI IDs values used in the IDs table
> > >> with the macros defined in pci_ids.h
> > >>
> > >Hi,
> > >
> > >hmm this is actually the opposite direction than most of the kernel is
> > >heading in, mostly because the pci_ids.h file is a major maintenance
> > >pain.
> > >
> > >Afaik the current "rule" is: if a PCI ID is only used in one driver, use
> > >the numeric value and not (add) a symbolic constant.
> > >
> >
> > My guess is that the RNG is on the LPC so the values are used in a few
> > places..
> >
>
> Will pci_ids.h be removed from the tree some time in the future then ?
No, it should contain ids that are used in multiple places (vendor ids
are one such example.)
And in this case, the majority of the patch is just using the vendor id,
which in my opinion, is a good idea.
thanks,
greg k-h
next prev parent reply other threads:[~2007-01-15 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 17:24 [PATCH 2.6.20-rc5] intel_rng: substitue magic PCI IDs with macros Ahmed S. Darwish
2007-01-14 17:37 ` Arjan van de Ven
2007-01-14 19:31 ` Dave Airlie
2007-01-14 23:07 ` Ahmed S. Darwish
2007-01-15 0:29 ` Greg KH [this message]
2007-01-15 7:16 ` Ahmed S. Darwish
2007-01-15 17:50 ` Ahmed S. Darwish
2007-01-15 0:29 ` Greg KH
2007-01-15 9:17 ` Ahmed S. Darwish
-- strict thread matches above, loose matches on Subject: below --
2007-01-15 20:38 Ahmed S. Darwish
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=20070115002924.GA20993@kroah.com \
--to=greg@kroah.com \
--cc=airlied@gmail.com \
--cc=arjan@infradead.org \
--cc=jgarzik@pobox.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