From: David Hinds <dhinds@sonic.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: (remove) event not supported.
Date: Sun, 01 Apr 2001 03:02:12 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98609425321805@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98597321622555@msgid-missing>
On Sun, Apr 01, 2001 at 06:53:01AM +1000, Brad Hards wrote:
> Also a good point, but in general, you don't want to do this. If there
> is a device still "connected" to the system, you don't want to remove
> the driver. For development, you might like to simulate a disconnection,
> but the normal approach is that you want support for every device that is
> connected to the system. Why remove a module for a device you are using?
Why?
Well the capability was one of the original reasons for creating
modules in the first place; they were not created for dynamic loading
of drivers for hot plug devices.
It is not an issue of removing a module for a device you are using;
you may want to remove a module for a device you are *not* using,
whether or not that device still happens to be present (and it may not
even be capable of removal).
-- dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-04-01 3:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 17:21 (remove) event not supported David Brownell
2001-03-31 1:00 ` Brad Hards
2001-03-31 2:03 ` Keith Owens
2001-03-31 2:12 ` Brad Hards
2001-03-31 3:48 ` David Hinds
2001-03-31 8:55 ` Brad Hards
2001-03-31 14:56 ` David Brownell
2001-03-31 15:02 ` David Brownell
2001-03-31 15:49 ` Keith Owens
2001-03-31 16:05 ` David Brownell
2001-03-31 16:18 ` Keith Owens
2001-03-31 16:52 ` David Brownell
2001-04-01 3:02 ` David Hinds [this message]
2001-04-01 3:03 ` David Hinds
2001-04-01 5:26 ` Douglas Gilbert
2001-04-02 2:56 ` Trond Eivind Glomsrød
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=marc-linux-hotplug-98609425321805@msgid-missing \
--to=dhinds@sonic.net \
--cc=linux-hotplug@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 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.