From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423298AbdEYBbb (ORCPT ); Wed, 24 May 2017 21:31:31 -0400 Received: from ozlabs.org ([103.22.144.67]:45041 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423282AbdEYBb2 (ORCPT ); Wed, 24 May 2017 21:31:28 -0400 Date: Thu, 25 May 2017 11:31:24 +1000 From: Stephen Rothwell To: David Sterba Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Liu Bo Subject: Re: linux-next: build warning after merge of the btrfs-kdave tree Message-ID: <20170525113124.44e4daf6@canb.auug.org.au> In-Reply-To: <20170518125000.GO4065@suse.cz> References: <20170518094146.7a1d9a2d@canb.auug.org.au> <20170518125000.GO4065@suse.cz> 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 David, On Thu, 18 May 2017 14:50:00 +0200 David Sterba wrote: > > On Thu, May 18, 2017 at 09:41:46AM +1000, Stephen Rothwell wrote: > > Hi David, > > > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > fs/btrfs/inode.c: In function 'btrfs_submit_direct': > > fs/btrfs/inode.c:8467:14: warning: 'bio' may be used uninitialized in this function [-Wmaybe-uninitialized] > > struct bio *bio; > > ^ > > > > I can't tell if it is a false positive or not. > > It seems to be a false positive. Patch updated and will be part of the > next for-next. I am still getting this. Just checking that you didn't forget to push. -- Cheers, Stephen Rothwell