From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755446AbdERMvB (ORCPT ); Thu, 18 May 2017 08:51:01 -0400 Received: from mx2.suse.de ([195.135.220.15]:35587 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753332AbdERMu7 (ORCPT ); Thu, 18 May 2017 08:50:59 -0400 Date: Thu, 18 May 2017 14:50:00 +0200 From: David Sterba To: Stephen Rothwell 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: <20170518125000.GO4065@suse.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Stephen Rothwell , Linux-Next Mailing List , Linux Kernel Mailing List , Liu Bo References: <20170518094146.7a1d9a2d@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170518094146.7a1d9a2d@canb.auug.org.au> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.