public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 21 Feb 2006 16:17:07 -0800	[thread overview]
Message-ID: <20060222001707.GA31611@kroah.com> (raw)
In-Reply-To: <20060221234807.GA27776@rescue.iwoars.net>

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.
> 
> Common scenario:
> A userspace application is notified that the ethernet cable was plugged
> out and later plugged in. It now checks whether the ethernet card is now
> connected to an other network and reassigns it's IP-Address via DHCP.
> 
> BTW: Of course I know that the constant KOBJ_ONLINE actually has an other
> meaning than what I used it for. I just didn't want to introduce a new
> constant and it just seems perfect for my purpose.
> 
> 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?

thanks,

greg k-h

  reply	other threads:[~2006-02-22  0:17 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 [this message]
2006-02-22  8:37   ` Thomas Ogrisegg
2006-02-22 17:53     ` Greg KH
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=20060222001707.GA31611@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox