From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Abdun Nihaal <abdun.nihaal@gmail•com>
Subject: Re: linux-next: build warnings after merge of the staging tree
Date: Mon, 14 May 2018 11:26:56 +0200 [thread overview]
Message-ID: <20180514092656.GB11384@kroah.com> (raw)
In-Reply-To: <20180514143404.28f0f4da@canb.auug.org.au>
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
next prev parent reply other threads:[~2018-05-14 9:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 4:34 linux-next: build warnings after merge of the staging tree Stephen Rothwell
2018-05-14 9:26 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-05 3:22 Stephen Rothwell
2019-02-05 10:24 ` Jonathan Cameron
2017-11-02 4:38 Stephen Rothwell
2017-07-31 5:02 Stephen Rothwell
2017-08-09 1:25 ` Stephen Rothwell
2017-08-22 1:49 ` Stephen Rothwell
2017-08-17 17:57 ` Greg KH
2017-08-18 12:02 ` JB Van Puyvelde
2015-05-29 10:40 Stephen Rothwell
2015-06-01 8:50 ` Stephen Rothwell
2015-06-20 10:48 ` Stephen Rothwell
2015-06-20 14:50 ` Greg KH
2015-05-06 4:10 Stephen Rothwell
2015-05-06 6:56 ` Julia Lawall
2012-01-31 3:25 Stephen Rothwell
2012-01-31 5:14 ` Greg KH
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=20180514092656.GB11384@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=abdun.nihaal@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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