From: Jeff Garzik <jeff@garzik.org>
To: Joe Perches <joe@perches.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] drivers/net/: use DEFINE_PCI_DEVICE_TABLE()
Date: Thu, 07 Jan 2010 17:28:00 -0500 [thread overview]
Message-ID: <4B465FF0.80802@garzik.org> (raw)
In-Reply-To: <1262903146.10429.83.camel@Joe-Laptop.home>
On 01/07/2010 05:25 PM, Joe Perches wrote:
> On Thu, 2010-01-07 at 23:58 +0200, Alexey Dobriyan wrote:
>> Use DEFINE_PCI_DEVICE_TABLE() so we get place PCI ids table into correct section
>> in every case.
>
> Good idea, but aren't there are some tables that are not const?
I hope not... those tables are read by userland tools.
Messing with the PCI ID tables as runtime is highly unusual, to say the
least.
Jeff
next prev parent reply other threads:[~2010-01-07 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 21:58 [PATCH] drivers/net/: use DEFINE_PCI_DEVICE_TABLE() Alexey Dobriyan
2010-01-07 22:25 ` Joe Perches
2010-01-07 22:28 ` Jeff Garzik [this message]
2010-01-08 7:34 ` Alexey Dobriyan
2010-01-08 7:54 ` David Miller
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=4B465FF0.80802@garzik.org \
--to=jeff@garzik.org \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).