public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build warning after merge of the f2fs tree
Date: Fri, 10 Feb 2017 10:51:35 +1100	[thread overview]
Message-ID: <20170210105135.26bc6739@canb.auug.org.au> (raw)

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

             reply	other threads:[~2017-02-09 23:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 23:51 Stephen Rothwell [this message]
2017-02-10  0:01 ` linux-next: build warning after merge of the f2fs tree Jaegeuk Kim
  -- strict thread matches above, loose matches on Subject: below --
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
2025-04-30 10:42 Stephen Rothwell

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=20170210105135.26bc6739@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=jaegeuk@kernel$(echo .)org \
    --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