diff options
author | David S. Miller <davem@davemloft.net> | 2017-04-05 08:14:14 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-04-05 08:14:14 -0700 |
commit | 2e507e24c90631f36b1c259d05b45f20630a2ad7 (patch) | |
tree | 30ec7b462b43d443fdb11712ee99ad953b5cf17c /lib/sg_split.c | |
parent | 589c49cbf9674808fd4ac9b7c17155abc0686f86 (diff) | |
parent | def12888c161e6fec0702e5ec9c3962846e3a21d (diff) |
Merge branch 'rtnetlink-event-type'
Vladislav Yasevich says:
====================
rtnetlink: Updates to rtnetlink_event()
This series came out of the conversation that started as a result
my first attempt to add netdevice event info to netlink messages.
This series converts event processing to a 'white list', where
we explicitely permit events to generate netlink messages. This
is meant to make people take a closer look and determine wheter
these events should really trigger netlink messages.
I am also adding a V2 of my patch to add event type to the netlink
message. This version supports all events that we currently generate.
I will also update my patch to iproute that will show this data
through 'ip monitor'.
I actually need the ability to trap NETDEV_NOTIFY_PEERS event
(as well as possible NETDEV_RESEND_IGMP) to support hanlding of
macvtap on top of bonding. I hope others will also find this info usefull.
V2: Added missed events (from David Ahern)
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib/sg_split.c')
0 files changed, 0 insertions, 0 deletions