From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jeff Layton <jlayton@poochiereds•net>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Jan Kara <jack@suse•cz>
Subject: linux-next: build warning after merge of the file-locks tree
Date: Wed, 21 Jun 2017 10:30:38 +1000 [thread overview]
Message-ID: <20170621103038.2b04a922@canb.auug.org.au> (raw)
Hi Jeff,
After merging the file-locks tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
mm/page-writeback.c: In function 'write_one_page':
mm/page-writeback.c:2380:15: warning: unused variable 'ret2' [-Wunused-variable]
int ret = 0, ret2;
^
Introduced by commit
4118ba44fa2c ("mm: clean up error handling in write_one_page")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-06-21 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 0:30 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-21 0:30 linux-next: build warning after merge of the file-locks tree Stephen Rothwell
2017-06-21 7:11 ` 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=20170621103038.2b04a922@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jack@suse$(echo .)cz \
--cc=jlayton@poochiereds$(echo .)net \
--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