From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Greg KH <greg@kroah.com>
Cc: 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 11:13:43 -0800 [thread overview]
Message-ID: <413920000.1048187623@flay> (raw)
In-Reply-To: <20030320192020.GB3315@kroah.com>
>> > 2.4.9 of course has the newstyle pci interface! And actual hotplug
>> > PCI support also is in all today singnificant 2.4.9 forks (RH..).
>> >
>> > There's even some shim to emulate the pci_driver style interface on
>> > 2.2.
>> >
>> > Anyway, this table has another use, it's used by userland ools like
>> > installers for selecting the right driver for a given pci device. So
>> > even if it seems unused from kernelspace it has a use.
>>
>> Are they kmem diving? Or parsing source code?
>
> They are looking at the modules.pcimap files which are generated from
> depmod, which pull it from the object files.
Hmmm ... so we're going to get a compiler warning for every hotpluggable
driver? or is this just an error in the way acenic does it? Seems like
the latter, but it's not clear to me how to fix it up properly ...
If it's the former, we need a better solution ;-)
M.
next prev parent reply other threads:[~2003-03-20 19:13 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 [this message]
2003-03-20 19:28 ` Jeff Garzik
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=413920000.1048187623@flay \
--to=mbligh@aracnet.com \
--cc=garzik@pobox.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jes@wildopensource.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