From: Xin Long
Date: Tue, 17 Oct 2017 18:28:45 +0800
> On Tue, Oct 17, 2017 at 5:59 PM, Jiri Pirko wrote:
>> Tue, Oct 17, 2017 at 11:39:38AM CEST, lucien@gmail.com wrote:
>>>It's better to send notifications to userspace by the events
>>>in rtnetlink_event, instead of calling rtmsg_ifinfo di
On Tue, Oct 17, 2017 at 6:38 PM, Jiri Pirko wrote:
> Tue, Oct 17, 2017 at 12:28:45PM CEST, lucien@gmail.com wrote:
>>On Tue, Oct 17, 2017 at 5:59 PM, Jiri Pirko wrote:
>>> Tue, Oct 17, 2017 at 11:39:38AM CEST, lucien@gmail.com wrote:
It's better to send notifications to userspace by t
Tue, Oct 17, 2017 at 12:28:45PM CEST, lucien@gmail.com wrote:
>On Tue, Oct 17, 2017 at 5:59 PM, Jiri Pirko wrote:
>> Tue, Oct 17, 2017 at 11:39:38AM CEST, lucien@gmail.com wrote:
>>>It's better to send notifications to userspace by the events
>>>in rtnetlink_event, instead of calling rtmsg
On Tue, Oct 17, 2017 at 5:59 PM, Jiri Pirko wrote:
> Tue, Oct 17, 2017 at 11:39:38AM CEST, lucien@gmail.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
Tue, Oct 17, 2017 at 11:39:38AM CEST, lucien@gmail.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_C
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 c
