From: Greg KH <greg@kroah.com>
To: Thomas Ogrisegg <tom-lkml@lkml.fnord.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netdev/uevent
Date: Wed, 22 Feb 2006 09:53:22 -0800 [thread overview]
Message-ID: <20060222175322.GA11733@kroah.com> (raw)
In-Reply-To: <20060222083751.GA12873@rescue.iwoars.net>
On Wed, Feb 22, 2006 at 09:37:51AM +0100, Thomas Ogrisegg wrote:
> On Tue, Feb 21, 2006 at 04:17:07PM -0800, Greg KH wrote:
> > On Wed, Feb 22, 2006 at 12:48:07AM +0100, Thomas Ogrisegg wrote:
> > > This patch adds userspace notification for register/unregister and
> > > plug/unplug events for netdevices. It calls kobject_uevent to let
> > > userspace applications (via netlink-interface) know that e.g. the
> > > ethernet-cable was plugged in (or plugged out) and thus the ethernet
> > > device may have to be reconfigured.
> [...]
> > > Signed-off-by: Thomas Ogrisegg <tom-lkml@lkml.fnord.at>
> > Hm, I thought ethtool and netlink already handled this kind of event
> > just fine. Why would you add a uevent too?
>
> What do you mean with "ethtool and netlink"? At least the current
> release of ethtool does not seem to have any netlink support.
That should have been "or", sorry.
> Is there currently any possibility for a program to get notified when
> a netdevice link becomes ready (or the opposite)? I don't see any interface
> (besides polling /sys).
Try asking on the netdev mailing list, I'm sure it must come up there a
lot.
thanks,
greg k-h
next prev parent reply other threads:[~2006-02-22 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 23:48 [PATCH] netdev/uevent Thomas Ogrisegg
2006-02-22 0:17 ` Greg KH
2006-02-22 8:37 ` Thomas Ogrisegg
2006-02-22 17:53 ` Greg KH [this message]
2006-02-22 17:54 ` Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2006-02-22 22:37 Stefan Rompf
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=20060222175322.GA11733@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom-lkml@lkml.fnord.at \
/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.