linux-kernel - Re: linux-next: build warnings after merge of the staging tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 14 May 2018 11:26:56 +0200
From:   Greg KH <greg@...ah.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Abdun Nihaal <abdun.nihaal@...il.com>
Subject: Re: linux-next: build warnings after merge of the staging tree

On Mon, May 14, 2018 at 02:34:04PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> drivers/staging/most/video/video.c: In function 'vidioc_enum_fmt_vid_cap':
> drivers/staging/most/video/video.c:265:25: warning: unused variable 'mdev' [-Wunused-variable]
>   struct most_video_dev *mdev = fh->mdev;
>                          ^~~~
> drivers/staging/most/video/video.c: In function 'vidioc_g_fmt_vid_cap':
> drivers/staging/most/video/video.c:282:25: warning: unused variable 'mdev' [-Wunused-variable]
>   struct most_video_dev *mdev = fh->mdev;
>                          ^~~~
> drivers/staging/most/video/video.c: In function 'vidioc_g_std':
> drivers/staging/most/video/video.c:309:25: warning: unused variable 'mdev' [-Wunused-variable]
>   struct most_video_dev *mdev = fh->mdev;
>                          ^~~~
> 
> Introduced by commit
> 
>   7d7cdb4fa552 ("staging: most: video: remove debugging code")

Sorry about this.  This warning, and the other one in the staging tree,
were not noticed by me due to my system updating to gcc-8 and the huge
numbers of warnings it produced.  Then 0-day went on a bender and didn't
spit out anything for a few days...

I'll go fix this up now, thanks for the report.

greg k-h