From: kernel test robot <lkp@intel.com>
To: Martin Hecht <mhecht73@gmail.com>, linux-media@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, sakari.ailus@linux.intel.com,
michael.roeder@avnet.eu, martin.hecht@avnet.eu,
Martin Hecht <mhecht73@gmail.com>,
Tommaso Merciai <tomm.merciai@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: i2c: alvium: Accelerated alvium_set_power
Date: Wed, 10 Sep 2025 10:31:16 +0800 [thread overview]
Message-ID: <202509101013.wDfoHTNv-lkp@intel.com> (raw)
In-Reply-To: <20250909112252.2577949-1-mhecht73@gmail.com>
Hi Martin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on sailus-media-tree/master]
[also build test WARNING on linuxtv-media-pending/master media-tree/master linus/master v6.17-rc5 next-20250909]
[cannot apply to sailus-media-tree/streams]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Martin-Hecht/media-i2c-alvium-Accelerated-alvium_set_power/20250909-193217
base: git://linuxtv.org/sailus/media_tree.git master
patch link: https://lore.kernel.org/r/20250909112252.2577949-1-mhecht73%40gmail.com
patch subject: [PATCH v2] media: i2c: alvium: Accelerated alvium_set_power
config: alpha-randconfig-r072-20250910 (https://download.01.org/0day-ci/archive/20250910/202509101013.wDfoHTNv-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250910/202509101013.wDfoHTNv-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509101013.wDfoHTNv-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/media/i2c/alvium-csi2.c: In function 'alvium_check':
>> drivers/media/i2c/alvium-csi2.c:2367:24: warning: unused variable 'dev' [-Wunused-variable]
2367 | struct device *dev = &alvium->i2c_client->dev;
| ^~~
vim +/dev +2367 drivers/media/i2c/alvium-csi2.c
2364
2365 static int alvium_check(struct alvium_dev *alvium, u64 *bcrm_major)
2366 {
> 2367 struct device *dev = &alvium->i2c_client->dev;
2368 int ret = 0;
2369
2370 ret = alvium_read(alvium, REG_BCRM_MAJOR_VERSION_R, bcrm_major, NULL);
2371
2372 if (ret)
2373 return ret;
2374
2375 if (*bcrm_major != 0)
2376 return 0;
2377
2378 return -ENODEV;
2379 }
2380
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-10 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 11:22 [PATCH v2] media: i2c: alvium: Accelerated alvium_set_power Martin Hecht
2025-09-10 2:31 ` kernel test robot [this message]
2025-09-10 15:09 ` Sakari Ailus
2025-09-10 17:17 ` Martin Hecht
2025-09-11 6:39 ` 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=202509101013.wDfoHTNv-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.hecht@avnet.eu \
--cc=mchehab@kernel.org \
--cc=mhecht73@gmail.com \
--cc=michael.roeder@avnet.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sakari.ailus@linux.intel.com \
--cc=tomm.merciai@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 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.