From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>,
Mauro Carvalho Chehab <mchehab@osg•samsung.com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
JB Van Puyvelde <jbvanpuyvelde@gmail•com>
Subject: Re: linux-next: build warnings after merge of the staging tree
Date: Wed, 9 Aug 2017 11:25:22 +1000 [thread overview]
Message-ID: <20170809112522.1b2563ad@canb.auug.org.au> (raw)
In-Reply-To: <20170731150227.58ea271b@canb.auug.org.au>
Hi all,
On Mon, 31 Jul 2017 15:02:27 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/staging/media/atomisp/i2c/imx/imx.c:1087:12: warning: 'imx_vcm_power_up' defined but not used [-Wunused-function]
> static int imx_vcm_power_up(struct v4l2_subdev *sd)
> ^
> drivers/staging/media/atomisp/i2c/imx/imx.c:1095:12: warning: 'imx_vcm_power_down' defined but not used [-Wunused-function]
> static int imx_vcm_power_down(struct v4l2_subdev *sd)
> ^
> drivers/staging/media/atomisp/i2c/imx/imx.c:1103:12: warning: 'imx_vcm_init' defined but not used [-Wunused-function]
> static int imx_vcm_init(struct v4l2_subdev *sd)
> ^
> drivers/staging/media/atomisp/i2c/imx/imx.c:1111:12: warning: 'imx_t_focus_vcm' defined but not used [-Wunused-function]
> static int imx_t_focus_vcm(struct v4l2_subdev *sd, u16 val)
> ^
>
> Introduced by commit
>
> 9a5a6911aa3f ("staging: imx: fix non-static declarations")
There is now another copy of this commit in the v4l-dvb tree producing
the same warnings :-(
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-08-09 1:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 5:02 linux-next: build warnings after merge of the staging tree Stephen Rothwell
2017-08-09 1:25 ` Stephen Rothwell [this message]
2017-08-22 1:49 ` Stephen Rothwell
2017-08-17 17:57 ` Greg KH
2017-08-18 12:02 ` JB Van Puyvelde
-- strict thread matches above, loose matches on Subject: below --
2019-02-05 3:22 Stephen Rothwell
2019-02-05 10:24 ` Jonathan Cameron
2018-05-14 4:34 Stephen Rothwell
2018-05-14 9:26 ` Greg KH
2017-11-02 4:38 Stephen Rothwell
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=20170809112522.1b2563ad@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=jbvanpuyvelde@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@osg$(echo .)samsung.com \
/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