From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754946AbcLNI0R (ORCPT ); Wed, 14 Dec 2016 03:26:17 -0500 Received: from ozlabs.org ([103.22.144.67]:46481 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754583AbcLNI0Q (ORCPT ); Wed, 14 Dec 2016 03:26:16 -0500 Date: Wed, 14 Dec 2016 19:26:09 +1100 From: Stephen Rothwell To: Richard Weinberger Cc: Ingo Molnar , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Artem Bityutskiy , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, David Gstir Subject: Re: linux-next: build warning after merge of the tip tree Message-ID: <20161214192609.36f6678c@canb.auug.org.au> In-Reply-To: References: <20161214132828.1d128963@canb.auug.org.au> <20161214072411.GA1635@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Richard, On Wed, 14 Dec 2016 09:05:10 +0100 Richard Weinberger 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