Re: linux-next: build warnings after merge of the file-locks tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx>




[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux