From: Christoph Hellwig <hch@infradead.org>
To: Jes Sorensen <jes@wildopensource.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.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 16:04:40 +0000 [thread overview]
Message-ID: <20030320160440.A14435@infradead.org> (raw)
In-Reply-To: <m365qenioq.fsf@trained-monkey.org>; from jes@wildopensource.com on Thu, Mar 20, 2003 at 10:47:49AM -0500
On Thu, Mar 20, 2003 at 10:47:49AM -0500, Jes Sorensen wrote:
> be. I have been reluctant to change the driver over to the new hotplug
> scheme since in the past there has been a significant number of AceNIC
> users running on older kernels which do not have the hotplug
> infrastructure (2.4.9 etc). On the other hand I don't remember hearing
> from a single person who wanted to use AceNIC in a hotplug
> environment.
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.
next prev parent reply other threads:[~2003-03-20 15:53 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 [this message]
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
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=20030320160440.A14435@infradead.org \
--to=hch@infradead.org \
--cc=garzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.