LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* linux-next: build warnings after merge of the file-locks tree
@ 2021-08-23  0:19 Stephen Rothwell
  2021-08-23 10:14 ` Jeff Layton
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2021-08-23  0:19 UTC (permalink / raw)
  To: Jeff Layton; +Cc: Linux Kernel Mailing List, Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

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")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: linux-next: build warnings after merge of the file-locks tree
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Jeff Layton @ 2021-08-23 10:14 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: Linux Kernel Mailing List, Linux Next Mailing List

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>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-08-23 10:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).