From: Jeff Layton <jlayton@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the file-locks tree
Date: Mon, 23 Aug 2021 06:14:23 -0400 [thread overview]
Message-ID: <934008823b152cbe9bf170c866d2c0aa8552e61e.camel@kernel.org> (raw)
In-Reply-To: <20210823101941.20ba89c3@canb.auug.org.au>
On Mon, 2021-08-23 at 10:19 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the file-locks tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/remap_range.c: In function 'remap_verify_area':
> fs/remap_range.c:102:16: warning: unused variable 'inode' [-Wunused-variable]
> 102 | struct inode *inode = file_inode(file);
> | ^~~~~
>
> Also from the arm multi_v7_defconfig build:
>
> fs/locks.c: In function 'fcntl_setlk64':
> fs/locks.c:2509:16: warning: unused variable 'inode' [-Wunused-variable]
> 2509 | struct inode *inode = locks_inode(filp);
> | ^~~~~
>
> And from the x86_64 allmodconfig build:
>
> fs/9p/vfs_file.c: In function 'v9fs_file_lock_dotl':
> fs/9p/vfs_file.c:322:1: warning: label 'out_err' defined but not used [-Wunused-label]
> 322 | out_err:
> | ^~~~~~~
>
> Introduced by commit
>
> 3efee0567b4a ("fs: remove mandatory file locking support")
>
Thanks Stephen. I'll fix those up.
Cheers,
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2021-08-23 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 0:19 linux-next: build warnings after merge of the file-locks tree Stephen Rothwell
2021-08-23 10:14 ` Jeff Layton [this message]
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=934008823b152cbe9bf170c866d2c0aa8552e61e.camel@kernel.org \
--to=jlayton@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).