Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, edumazet@google.com,
	alexander.h.duyck@intel.com, xiyou.wangcong@gmail.com
Subject: Re: [patch net-next] net: add netnotifier event for upper device change
Date: Sun, 26 May 2013 09:10:39 +0200	[thread overview]
Message-ID: <20130526071039.GA1560@minipsycho.orion> (raw)
In-Reply-To: <20130525.231413.1228840457158928295.davem@davemloft.net>

Sun, May 26, 2013 at 08:14:13AM CEST, davem@davemloft.net wrote:
>From: Jiri Pirko <jiri@resnulli.us>
>Date: Sat, 25 May 2013 16:12:10 +0200
>
>> Now when upper device is changed, event is not propagated via RT Netlink
>> to userspace. Userspace might never now about the change. Fix this by
>> adding upper-device-change notifier event.
>> 
>> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>
>Looks good, applied, thanks Jiri.
>
>If someone is looking for a useful project, switching networking over to
>a more typed notifier system would be a worthwhile improvement.
>
>It's hard to right now to communicate what changed beyond "action X
>happened to this object, you have to check to see exactly how it
>changed"

Hmm. Do you have something particular in mind? My first thought was
passing some union instead of NETDEV_* numbers.

>
>This came up recently with the IFF_NOARP stuff.

Can you point me to the discussion?

Thanks

Jiri

  reply	other threads:[~2013-05-26  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 14:12 [patch net-next] net: add netnotifier event for upper device change Jiri Pirko
2013-05-26  6:14 ` David Miller
2013-05-26  7:10   ` Jiri Pirko [this message]
2013-05-26  7:37     ` David Miller

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=20130526071039.GA1560@minipsycho.orion \
    --to=jiri@resnulli.us \
    --cc=alexander.h.duyck@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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