[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180104165217.7737a0bc@canb.auug.org.au>
Date: Thu, 4 Jan 2018 16:52:17 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Steve French <smfrench@...il.com>
Cc: CIFS <linux-cifs@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Long Li <longli@...rosoft.com>,
Pavel Shilovsky <pshilov@...rosoft.com>,
Ronnie Sahlberg <lsahlber@...hat.com>
Subject: Re: linux-next: build warning after merge of the cifs tree
Hi Steve,
On Wed, 3 Jan 2018 16:44:59 -0600 Steve French <smfrench@...il.com> wrote:
>
> I don't see this with gcc 5.4
Good to know.
> Harmless to initialize flags here ... even if unneeded ... so if it
> makes your life easier I don't mind initializes to 0. Let me know.
> Wonder why it doesn't generate the warning on the various other places
> in the fs that do the same thing?
I might just take the hint to upgrade my cross compilers :-) Thanks anyway.
In the mean time, my scripts will automatically skip reporting this
warning to me.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists