public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Greg KH <greg@kroah.com>, Christoph Hellwig <hch@infradead.org>,
	Jes Sorensen <jes@wildopensource.com>,
	Jeff Garzik <garzik@pobox.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fixup warning for acenic
Date: Thu, 20 Mar 2003 14:28:36 -0500	[thread overview]
Message-ID: <20030320192836.GD8256@gtf.org> (raw)
In-Reply-To: <413920000.1048187623@flay>

On Thu, Mar 20, 2003 at 11:13:43AM -0800, Martin J. Bligh wrote:
> Hmmm ... so we're going to get a compiler warning for every hotpluggable
> driver?

Only for the ones that do not actually use the module_device_table,
which is an unusual case.

Adam Richter(sp?) went through and added PCI module_device_tables to
drivers which do not use the PCI API.  From the programmer's standpoint
this looks like dead code -- but it's actually very useful, because it
exports the PCI ids to userspace in
/lib/modules/`uname -r`/modules.pcimap, where installers, hardware
configurators, and other tools pick up the data and do something useful
with it.

	Jeff




  reply	other threads:[~2003-03-20 19:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20  7:50 [PATCH] Fixup warning for acenic Martin J. Bligh
2003-03-20 15:47 ` Jes Sorensen
2003-03-20 16:04   ` Christoph Hellwig
2003-03-20 16:11     ` Martin J. Bligh
2003-03-20 19:20       ` Greg KH
2003-03-20 19:13         ` Martin J. Bligh
2003-03-20 19:28           ` Jeff Garzik [this message]
2003-03-20 19:30           ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-03-20 15:17 Matthew Wilcox
2003-03-20 15:50 ` Martin J. Bligh
2003-03-20 15:59   ` Matthew Wilcox
2003-03-20 16:10     ` Martin J. Bligh

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=20030320192836.GD8256@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=garzik@pobox.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=jes@wildopensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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