From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Tuukka Toivonen <tuukkat76@gmail.com>,
Pavel Machek <pavel@ucw.cz>,
linux-media@vger.kernel.org
Subject: Re: [GIT PULL FOR v4.11] Add et8ek8 driver
Date: Tue, 31 Jan 2017 11:01:11 -0200 [thread overview]
Message-ID: <20170131110111.06321f77@vento.lan> (raw)
In-Reply-To: <20170131124534.GW7139@valkosipuli.retiisi.org.uk>
Em Tue, 31 Jan 2017 14:45:34 +0200
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> Hi Mauro,
>
> On Tue, Jan 31, 2017 at 10:42:48AM -0200, Mauro Carvalho Chehab wrote:
> > That added a new warning:
> >
> > drivers/media/i2c/et8ek8/et8ek8_driver.c: In function 'et8ek8_registered':
> > drivers/media/i2c/et8ek8/et8ek8_driver.c:1262:29: warning: variable 'format' set but not used [-Wunused-but-set-variable]
> > struct v4l2_mbus_framefmt *format;
> > ^~~~~~
> > compilation succeeded
> >
> >
> > The driver is calling this function and storing it on a var
> > that is not used:
> >
> > format = __et8ek8_get_pad_format(sensor, NULL, 0,
> > V4L2_SUBDEV_FORMAT_ACTIVE);
> > return 0;
> >
> > Please send a fixup patch.
>
> I compiled it, too, but I guess I had a GCC version that didn't complain
> about this particular matter. I'll send you a fix.
I run make with "W=1", to enable a few extra warnings that are usually
troubles, like the above. W=2 would point some other things, but
IMHO, it is not worth trying to fix the extra warnings, as it will enable
a lot of signed/unsigned errors with are usually OK.
Thanks,
Mauro
next prev parent reply other threads:[~2017-01-31 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 14:07 [GIT PULL FOR v4.11] Add et8ek8 driver Sakari Ailus
2017-01-31 12:42 ` Mauro Carvalho Chehab
2017-01-31 12:45 ` Sakari Ailus
2017-01-31 13:01 ` Mauro Carvalho Chehab [this message]
2017-02-01 12:47 ` Sakari Ailus
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=20170131110111.06321f77@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-media@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sakari.ailus@iki.fi \
--cc=tuukkat76@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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