From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Sterba <dsterba@suse•cz>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Liu Bo <bo.li.liu@oracle•com>
Subject: Re: linux-next: build warning after merge of the btrfs-kdave tree
Date: Thu, 25 May 2017 11:31:24 +1000 [thread overview]
Message-ID: <20170525113124.44e4daf6@canb.auug.org.au> (raw)
In-Reply-To: <20170518125000.GO4065@suse.cz>
Hi David,
On Thu, 18 May 2017 14:50:00 +0200 David Sterba <dsterba@suse•cz> 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
next prev parent reply other threads:[~2017-05-25 1:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 23:41 linux-next: build warning after merge of the btrfs-kdave tree Stephen Rothwell
2017-05-18 12:50 ` David Sterba
2017-05-25 1:31 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-03 0:21 Stephen Rothwell
2019-05-03 13:37 ` David Sterba
2019-01-23 22:53 Stephen Rothwell
2019-01-28 16:53 ` David Sterba
2018-11-26 0:06 Stephen Rothwell
2018-11-26 7:56 ` Christoph Hellwig
2017-12-19 22:20 Stephen Rothwell
2017-12-20 0:12 ` Qu Wenruo
2017-12-21 16:49 ` David Sterba
2017-12-22 0:32 ` Qu Wenruo
2016-11-28 0:02 Stephen Rothwell
2016-12-06 22:38 ` Stephen Rothwell
2016-12-14 15:19 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170525113124.44e4daf6@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bo.li.liu@oracle$(echo .)com \
--cc=dsterba@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox