[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190329153423.GZ14297@nanopsycho>
Date: Fri, 29 Mar 2019 16:34:23 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Si-Wei Liu <si-wei.liu@...cle.com>, mst@...hat.com,
sridhar.samudrala@...el.com, davem@...emloft.net, kubakici@...pl,
alexander.duyck@...il.com, netdev@...r.kernel.org,
virtualization@...ts.linux-foundation.org, liran.alon@...cle.com,
boris.ostrovsky@...cle.com, vijay.balakrishna@...cle.com
Subject: Re: [PATCH net v4] failover: allow name change on IFF_UP slave
interfaces
Fri, Mar 29, 2019 at 04:15:12PM CET, stephen@...workplumber.org wrote:
>On Thu, 28 Mar 2019 19:47:27 -0400
>Si-Wei Liu <si-wei.liu@...cle.com> wrote:
>
>> + if (unlikely(dev->flags & IFF_UP)) {
>> + struct netdev_notifier_change_info change_info;
>> +
>> + change_info.flags_changed = 0;
>
>Simpler to use structure initialization, which also avoid any chance
>of unititialized fields.
>
> struct netdev_notifier_change_info change_info
> = { .flags_changed = 0 };
In fact, you can do just:
struct netdev_notifier_change_info change_info = {};
to achieve the same.
Powered by blists - more mailing lists