[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65d65f35-5991-7131-66f3-7998914db92f@gmail.com>
Date: Tue, 30 May 2017 08:22:31 -0600
From: David Ahern <dsahern@...il.com>
To: Vladislav Yasevich <vyasevich@...il.com>, netdev@...r.kernel.org
Cc: roopa@...ulusnetworks.com, jiri@...nulli.us, vfalico@...il.com,
andy@...yhouse.net, Vladislav Yasevich <vyasevic@...hat.com>
Subject: Re: [PATCH V6 net-next iproute] ip: Add support for netdev events to
monitor
On 5/27/17 8:14 AM, Vladislav Yasevich wrote:
> diff --git a/ip/ipaddress.c b/ip/ipaddress.c
> index b8d9c7d..c6e7413 100644
> --- a/ip/ipaddress.c
> +++ b/ip/ipaddress.c
> @@ -753,6 +753,24 @@ int print_linkinfo_brief(const struct sockaddr_nl *who,
> return 0;
> }
>
> +static const char *netdev_events[] = {"NONE",
I would prefer ifla_events rather than netdev just to reinforce the
separation that an IFLA_EVENT does not necessarily correspond to a
NETDEV event.
Powered by blists - more mailing lists