From: Andrew Morton <andrewm@uow.edu.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: Network hotplug semantics
Date: Fri, 09 Feb 2001 01:27:32 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98168247104499@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98161573514987@msgid-missing>
David Brownell wrote:
>
> Today, hotplug events basically involve namespace update activities:
> for network hotplug events it's just "register" or "unregister". No
> event corresponds to "plugged".
There's netif_carrier_on and _off. Practically no drivers use
this at present. Better netdevice manageability is on the
2.5 dartboard somewhere.
_______________________________________________
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-02-09 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 7:02 Network hotplug semantics Matthew Dharm
2001-02-08 7:03 ` Brad Hards
2001-02-08 8:32 ` Oliver Neukum
2001-02-09 0:28 ` David Brownell
2001-02-09 1:27 ` Andrew Morton [this message]
2001-02-10 3:46 ` Brad Hards
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-98168247104499@msgid-missing \
--to=andrewm@uow.edu.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).