From: kbuild test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@01.org, Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Cox <alan@linux.intel.com>,
devel@driverdev.osuosl.org, Arnd Bergmann <arnd@arndb.de>,
Varsha Rao <rvarsha016@gmail.com>,
sayli karnik <karniksayli1995@gmail.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] staging: atomisp: avoid false-positive maybe-uninitialized warning
Date: Wed, 29 Mar 2017 04:10:37 +0800 [thread overview]
Message-ID: <201703290457.BJ1KohSr%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170328100321.3836826-1-arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 2358 bytes --]
Hi Arnd,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on next-20170328]
[cannot apply to linuxtv-media/master v4.11-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/staging-atomisp-avoid-false-positive-maybe-uninitialized-warning/20170329-023715
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/staging/media/atomisp/i2c/mt9m114.c: In function 'mt9m114_get_fmt':
>> drivers/staging/media/atomisp/i2c/mt9m114.c:818:25: error: unused variable 'dev' [-Werror=unused-variable]
struct mt9m114_device *dev = to_mt9m114_sensor(sd);
^~~
drivers/staging/media/atomisp/i2c/mt9m114.c: In function 'mt9m114_s_exposure_selection':
drivers/staging/media/atomisp/i2c/mt9m114.c:1179:25: error: unused variable 'dev' [-Werror=unused-variable]
struct mt9m114_device *dev = to_mt9m114_sensor(sd);
^~~
cc1: all warnings being treated as errors
vim +/dev +818 drivers/staging/media/atomisp/i2c/mt9m114.c
a49d2536 Alan Cox 2017-02-17 812
a49d2536 Alan Cox 2017-02-17 813 static int mt9m114_get_fmt(struct v4l2_subdev *sd,
a49d2536 Alan Cox 2017-02-17 814 struct v4l2_subdev_pad_config *cfg,
a49d2536 Alan Cox 2017-02-17 815 struct v4l2_subdev_format *format)
a49d2536 Alan Cox 2017-02-17 816 {
a49d2536 Alan Cox 2017-02-17 817 struct v4l2_mbus_framefmt *fmt = &format->format;
a49d2536 Alan Cox 2017-02-17 @818 struct mt9m114_device *dev = to_mt9m114_sensor(sd);
a49d2536 Alan Cox 2017-02-17 819 int width, height;
a49d2536 Alan Cox 2017-02-17 820 int ret;
a49d2536 Alan Cox 2017-02-17 821 if (format->pad)
:::::: The code at line 818 was first introduced by commit
:::::: a49d25364dfb9f8a64037488a39ab1f56c5fa419 staging/atomisp: Add support for the Intel IPU v2
:::::: TO: Alan Cox <alan@linux.intel.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 59110 bytes --]
next prev parent reply other threads:[~2017-03-28 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 10:02 Arnd Bergmann
2017-03-28 20:10 ` kbuild test robot [this message]
2017-03-28 20:40 ` Arnd Bergmann
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=201703290457.BJ1KohSr%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=karniksayli1995@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rvarsha016@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
all inboxes | Powered by JetHome®