From: David Hinds <dhinds@sonic.net>
To: Andrew Morton <andrewm@uow.edu.au>,
Manfred Spraul <manfred@colorfullife.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] network driver updates
Date: Thu, 15 Feb 2001 09:08:07 -0800 [thread overview]
Message-ID: <20010215090807.C29356@sonic.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1010214020707.28011E-100000@mandrakesoft.mandrakesoft.com> <3A8A7159.AF0E6180@colorfullife.com> <3A8A8937.A77BA18D@uow.edu.au> <20010214093859.B20503@sonic.net> <3A8AC6B6.9790FF9C@colorfullife.com> <3A8BC242.2C62DAA1@uow.edu.au>
In-Reply-To: <3A8BC242.2C62DAA1@uow.edu.au>; from Andrew Morton on Thu, Feb 15, 2001 at 10:49:22PM +1100
On Thu, Feb 15, 2001 at 10:49:22PM +1100, Andrew Morton wrote:
>
> Now, the thing I don't understand about David's design is the
> final one. What 3c575_cb does is:
>
> CONFIG_HOTPLUG=y, MODULE=true
> If the hardware isn't there, register the driver and
> hang around.
>
> Why?
Merely that I was trying to disassociate the concepts of module
loading and device probing, and I thought it was most consistent to
then allow people to load modules whenever they want, whether or not a
device was present.
> BTW: How come CONFIG_PCMCIA requires CONFIG_HOTPLUG? Doesn't
> it make sense to be able to have glued-in Cardbus devices?
I suppose it makes sense but I don't know if it is something worth the
trouble of supporting.
-- Dave
next prev parent reply other threads:[~2001-02-15 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.1010214020707.28011E-100000@mandrakesoft.mandrakesoft.com>
2001-02-14 11:51 ` [PATCH] network driver updates Manfred Spraul
2001-02-14 11:54 ` Jeff Garzik
2001-02-14 13:13 ` Arnaldo Carvalho de Melo
2001-02-14 12:00 ` Jeff Garzik
2001-02-14 13:33 ` Andrew Morton
2001-02-14 17:38 ` David Hinds
2001-02-14 17:54 ` Jeff Garzik
2001-02-14 17:56 ` Manfred Spraul
2001-02-15 11:49 ` Andrew Morton
2001-02-15 17:08 ` David Hinds [this message]
2001-02-15 22:16 ` Andrew Morton
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=20010215090807.C29356@sonic.net \
--to=dhinds@sonic.net \
--cc=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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