From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the f2fs tree
Date: Thu, 9 Feb 2017 16:01:52 -0800 [thread overview]
Message-ID: <20170210000152.GA20930@jaegeuk.local> (raw)
In-Reply-To: <20170210105135.26bc6739@canb.auug.org.au>
Thank you.
Worked around that in the dev branch.
On 02/10, Stephen Rothwell wrote:
> Hi Jaegeuk,
>
> After merging the f2fs tree, today's linux-next build
> (x86_64_allmodconfig) produced this warning:
>
> fs/f2fs/node.c: In function 'fsync_node_pages':
> fs/f2fs/node.c:1520:3: warning: 'last_idx' may be used uninitialized in this function [-Wmaybe-uninitialized]
> f2fs_submit_merged_bio_cond(sbi, NULL, ino, last_idx,
> ^
>
> Introduced by commit
>
> 9563642a6ec2 ("f2fs: check last page index in cached bio to decide submission")
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2017-02-10 0:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 23:51 linux-next: build warning after merge of the f2fs tree Stephen Rothwell
2017-02-10 0:01 ` Jaegeuk Kim [this message]
2018-11-26 0:19 Stephen Rothwell
2018-11-26 21:59 ` Jaegeuk Kim
2018-11-26 22:17 ` Stephen Rothwell
2018-11-26 22:22 ` Jaegeuk Kim
2018-11-26 22:36 ` Gustavo A. R. Silva
2018-11-26 22:40 ` Stephen Rothwell
2021-01-07 3:11 Stephen Rothwell
2021-01-07 11:28 ` Chao Yu
2021-01-10 20:33 ` Stephen Rothwell
2021-01-10 23:35 ` Jonathan Corbet
2021-01-11 7:54 ` Chao Yu
2021-01-12 5:09 ` Stephen Rothwell
2021-01-12 6:07 ` Chao Yu
2021-03-02 22:23 Stephen Rothwell
2021-03-03 19:27 ` Jaegeuk Kim
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=20170210000152.GA20930@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).