[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADvbK_c7R2OJNq=DyXOCSNVzD2aU2qxBO6UiitGbCYS=icwxTQ@mail.gmail.com>
Date: Tue, 17 Oct 2017 18:28:45 +0800
From: Xin Long <lucien.xin@...il.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: network dev <netdev@...r.kernel.org>, davem <davem@...emloft.net>
Subject: Re: [PATCH net 0/3] bonding: void calling rtmsg_ifinfo for netlink notifications
On Tue, Oct 17, 2017 at 5:59 PM, Jiri Pirko <jiri@...nulli.us> wrote:
> Tue, Oct 17, 2017 at 11:39:38AM CEST, lucien.xin@...il.com wrote:
>>It's better to send notifications to userspace by the events
>>in rtnetlink_event, instead of calling rtmsg_ifinfo directly.
>>
>>This patcheset is to remove rtmsg_ifinfo called in bonding,
>>the notifications can be handled by NETDEV_CHANGEUPPER and
>>NETDEV_CHANGELOWERSTATE events in rtnetlink_event.
>>
>>It could also fix some redundant notifications from bonding.
>
> This should go to net-next.
NETDEV_CHANGEUPPER is not yet in rtnetlink_event in net-next tree.
patches can only work on net tree by now.
Hi, David, you want me to hold them until the patches for NETDEV_CHANGEUPPER
are copied to net-next, or you would apply them to net ?
>
>
>>
>>Xin Long (3):
>> bonding: remove rtmsg_ifinfo called in bond_master_upper_dev_link
>> rtnetlink: bring NETDEV_CHANGELOWERSTATE event process back to
>> rtnetlink_event
>> bonding: remove rtmsg_ifinfo called after bond_lower_state_changed
>>
>> drivers/net/bonding/bond_main.c | 11 +++--------
>> include/net/bonding.h | 4 ----
>> net/core/rtnetlink.c | 2 +-
>> 3 files changed, 4 insertions(+), 13 deletions(-)
>>
>>--
>>2.1.0
>>
Powered by blists - more mailing lists