From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: Re: linux-next: build warning after merge of the pm tree
Date: Tue, 31 Jul 2018 10:39:23 +1000 [thread overview]
Message-ID: <20180731103923.47c7c294@canb.auug.org.au> (raw)
In-Reply-To: <20180730072445.kt2yxxifx4i7y3fr@paasikivi.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Hi all,
On Mon, 30 Jul 2018 10:24:45 +0300 Sakari Ailus <sakari.ailus@linux.intel.com> wrote:
>
> On Mon, Jul 30, 2018 at 12:00:53PM +1000, Stephen Rothwell wrote:
> >
> > After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> >
> > drivers/media/i2c/mt9v111.c: In function 'mt9v111_set_format':
> > drivers/media/i2c/mt9v111.c:887:15: warning: 'idx' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > unsigned int idx;
> > ^~~
> >
> > Introduced by commit
> >
> > aab7ed1c3927 ("media: i2c: Add driver for Aptina MT9V111")
> >
> > Looks like a false positive, but not something that gcc can easily see.
>
> This must be coming from a new driver merged to media tree recently. Thanks
> for reporting this.
Yeah, sorry, process failure. This should have been reported against
the v4l-dvb tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-31 0:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 2:00 linux-next: build warning after merge of the pm tree Stephen Rothwell
2018-07-30 7:24 ` Sakari Ailus
2018-07-30 7:30 ` jacopo mondi
2018-07-31 0:39 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 5:00 Stephen Rothwell
2024-02-05 5:30 ` Meng, Li (Jassmine)
2022-02-06 22:40 Stephen Rothwell
2021-10-13 6:28 Stephen Rothwell
2022-01-17 22:02 ` Stephen Rothwell
2021-03-31 0:29 Stephen Rothwell
2021-03-31 6:22 ` Vitaly Kuznetsov
2021-04-02 17:18 ` Rafael J. Wysocki
2021-02-15 0:39 Stephen Rothwell
2021-02-15 0:39 ` Stephen Rothwell
2021-02-15 10:23 ` Andy Shevchenko
2021-02-15 10:23 ` Andy Shevchenko
2021-02-15 10:24 ` Andy Shevchenko
2021-02-15 10:24 ` Andy Shevchenko
2021-02-22 8:34 ` Stephen Rothwell
2021-02-22 8:34 ` Stephen Rothwell
2021-01-27 1:43 Stephen Rothwell
2021-01-27 3:54 ` Zhang Rui
2020-11-19 0:09 Stephen Rothwell
2020-11-19 16:22 ` Andy Shevchenko
2020-09-22 8:11 Stephen Rothwell
2020-10-01 9:43 ` Stephen Rothwell
2020-10-08 9:35 ` Stephen Rothwell
2020-10-15 7:20 ` Stephen Rothwell
2020-07-30 2:55 Stephen Rothwell
2020-07-30 3:10 ` Neal Liu
2020-01-19 23:40 Stephen Rothwell
2019-10-14 23:08 Stephen Rothwell
2019-10-15 8:23 ` Andy Shevchenko
2019-10-15 9:41 ` Rafael J. Wysocki
[not found] <201907111346291954773@zte.com.cn>
2019-07-11 12:26 ` Rafael J. Wysocki
2019-07-11 1:31 Stephen Rothwell
2019-01-23 23:45 Stephen Rothwell
2018-06-08 0:30 Stephen Rothwell
2018-06-08 9:14 ` Rafael J. Wysocki
2018-04-09 1:24 Stephen Rothwell
2018-04-10 7:05 ` Rafael J. Wysocki
2016-11-13 23:40 Stephen Rothwell
2016-11-14 0:03 ` Rafael J. Wysocki
2016-11-14 8:49 ` Akshay Adiga
2014-11-17 2:44 Stephen Rothwell
2014-11-17 11:31 ` Paul Bolle
2014-11-17 23:14 ` Rafael J. Wysocki
2014-11-17 23:45 ` Paul Bolle
2014-11-18 0:34 ` Rafael J. Wysocki
2014-10-29 2:51 Stephen Rothwell
2014-10-29 14:55 ` Rafael J. Wysocki
2014-10-29 15:23 ` Fengguang Wu
2014-10-29 15:56 ` Rafael J. Wysocki
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=20180731103923.47c7c294@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.