From: "Kay Sievers" <kay.sievers@vrfy.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
David Miller <davem@davemloft.net>,
Marcel Holtmann <marcel@holtmann.org>,
linux-hotplug@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] netdev: generate kobject uevent on network state transitions
Date: Tue, 25 Nov 2008 03:08:32 +0000 [thread overview]
Message-ID: <ac3eb2510811241908w3d8db29ai7e2ff98d4f8f6edd@mail.gmail.com> (raw)
In-Reply-To: <20081124150347.73050f98@extreme>
On Tue, Nov 25, 2008 at 00:03, Stephen Hemminger <shemminger@vyatta.com> wrote:
> It is easier for some applications to deal with text based interfaces
> like uevent, rather than using netlink to listen for events.
>
> Note, this does not deal with network namespaces but that is a generic
> problem that already exists with kobjects (see rename events).
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Works fine here.
Thanks,
Kay
next prev parent reply other threads:[~2008-11-25 3:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 7:41 [RFC] network devices generating uevents? Stephen Hemminger
2008-11-22 14:08 ` Kay Sievers
2008-11-22 19:22 ` Karl O. Pinc
2008-11-23 2:13 ` Marcel Holtmann
2008-11-23 6:32 ` Stephen Hemminger
2008-11-23 16:13 ` Kay Sievers
2008-11-24 19:45 ` [PATCH] netdev: generate kobject uevent on network events Stephen Hemminger
2008-11-24 19:55 ` Kay Sievers
2008-11-24 20:06 ` Stephen Hemminger
2008-11-25 8:39 ` David Miller
2008-11-24 20:06 ` Ben Hutchings
2008-11-24 23:03 ` [PATCH] netdev: generate kobject uevent on network state Stephen Hemminger
2008-11-25 3:08 ` Kay Sievers [this message]
2008-11-25 3:51 ` [PATCH] netdev: generate kobject uevent on network state transitions Marcel Holtmann
2008-11-25 4:14 ` [PATCH] netdev: generate kobject uevent on network state Stephen Hemminger
2008-11-25 9:09 ` David Miller
2008-11-26 5:24 ` [PATCH] netdev: generate kobject uevent on network state transitions Marcel Holtmann
2008-11-26 12:09 ` Kay Sievers
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=ac3eb2510811241908w3d8db29ai7e2ff98d4f8f6edd@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-hotplug@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).