[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <FB30A309-CE17-43E7-8B5B-BC276E849720@holtmann.org>
Date: Wed, 26 Nov 2008 06:24:47 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: David Miller <davem@...emloft.net>
Cc: shemminger@...tta.com, bhutchings@...arflare.com,
kay.sievers@...y.org, linux-hotplug@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH] netdev: generate kobject uevent on network state transitions
Hi Dave,
>>>> 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@...tta.com>
> ...
>>> do we wanna copy just what ifconfig shows or do we might be a more
>>> intelligent and have separate variables like RUNNING=1 etc.?
>>
>> Was arbitrary choice to just use same flags as existing ifconfig.
>> What ever feels best I guess...
>
> So what do folks want me to do here? Should I put Stephen's
> latest patch in, or do we want to make some kind of flags change?
I am thinking of using per value variables. My personal choice.
Kay, any pointers or opinions from you?
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists