[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161214192609.36f6678c@canb.auug.org.au>
Date: Wed, 14 Dec 2016 19:26:09 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Richard Weinberger <richard@....at>
Cc: Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Artem Bityutskiy <dedekind1@...il.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
David Gstir <david@...ma-star.at>
Subject: Re: linux-next: build warning after merge of the tip tree
Hi Richard,
On Wed, 14 Dec 2016 09:05:10 +0100 Richard Weinberger <richard@....at> wrote:
>
> The commit comes via my UBIFS tree. But I never saw this warning, I'm testing with both gcc-4.8 and gcc-6.1.
> Let me investigate into that.
>
> Does today's tip change some compiler flags?
Linus' tree commit
a76bcf557ef4 ("Kbuild: enable -Wmaybe-uninitialized warning for "make W=1"")
was introduced between -rc4 and -rc5 so it is not in your tree.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists