From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752208AbeADFwW (ORCPT + 1 other); Thu, 4 Jan 2018 00:52:22 -0500 Received: from ozlabs.org ([103.22.144.67]:41613 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751054AbeADFwU (ORCPT ); Thu, 4 Jan 2018 00:52:20 -0500 Date: Thu, 4 Jan 2018 16:52:17 +1100 From: Stephen Rothwell To: Steve French Cc: CIFS , Linux-Next Mailing List , Linux Kernel Mailing List , Long Li , Pavel Shilovsky , Ronnie Sahlberg Subject: Re: linux-next: build warning after merge of the cifs tree Message-ID: <20180104165217.7737a0bc@canb.auug.org.au> In-Reply-To: References: <20180104093359.4e012f2f@canb.auug.org.au> 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 Return-Path: Hi Steve, On Wed, 3 Jan 2018 16:44:59 -0600 Steve French 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