From: kernel test robot <lkp@intel.com>
To: Guo Zihao <guozh23@xiaopeng.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Liu Chao <liuc63@xiaopeng.com>
Subject: Re: [PATCH] media: cobalt: bound the dv timings to the descriptor buffers
Date: Sat, 19 Sep 2026 09:51:05 +0800 [thread overview]
Message-ID: <202609190912.ouKMS0Bi-lkp@intel.com> (raw)
In-Reply-To: <20260918072526.2478529-1-guozh23@xiaopeng.com>
Hi Guo,
kernel test robot noticed the following build errors:
[auto build test ERROR on linuxtv-media-pending/master]
[also build test ERROR on media-tree/master sailus-media-tree/master linus/master sailus-media-tree/streams v7.3-rc3 next-20260918]
[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/Guo-Zihao/media-cobalt-bound-the-dv-timings-to-the-descriptor-buffers/20260918-152526
base: https://git.linuxtv.org/media-ci/media-pending.git master
patch link: https://lore.kernel.org/r/20260918072526.2478529-1-guozh23%40xiaopeng.com
patch subject: [PATCH] media: cobalt: bound the dv timings to the descriptor buffers
config: arm-randconfig-r1300-20260918 (https://download.01.org/0day-ci/archive/20260919/202609190912.ouKMS0Bi-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260919/202609190912.ouKMS0Bi-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/202609190912.ouKMS0Bi-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/asm-generic/bug.h:31,
from arch/arm/include/asm/bug.h:60,
from include/linux/bug.h:5,
from include/linux/thread_info.h:13,
from include/linux/sched.h:14,
from include/linux/ratelimit.h:6,
from include/linux/dev_printk.h:16,
from include/linux/device.h:15,
from include/linux/dma-mapping.h:5,
from drivers/media/pci/cobalt/cobalt-v4l2.c:11:
drivers/media/pci/cobalt/cobalt-v4l2.c: In function 'cobalt_s_dv_timings':
>> drivers/media/pci/cobalt/cobalt-driver.h:160:45: error: 'cobalt' undeclared (first use in this function)
160 | #define cobalt_info(fmt, arg...) v4l2_info(&cobalt->v4l2_dev, fmt, ## arg)
| ^~~~~~
include/linux/printk.h:483:33: note: in definition of macro 'printk_index_wrap'
483 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/media/v4l2-common.h:58:9: note: in expansion of macro 'printk'
58 | printk(level "%s: " fmt, (dev)->name , ## arg)
| ^~~~~~
include/media/v4l2-common.h:67:9: note: in expansion of macro 'v4l2_printk'
67 | v4l2_printk(KERN_INFO, dev, fmt , ## arg)
| ^~~~~~~~~~~
drivers/media/pci/cobalt/cobalt-driver.h:160:34: note: in expansion of macro 'v4l2_info'
160 | #define cobalt_info(fmt, arg...) v4l2_info(&cobalt->v4l2_dev, fmt, ## arg)
| ^~~~~~~~~
drivers/media/pci/cobalt/cobalt-v4l2.c:635:17: note: in expansion of macro 'cobalt_info'
635 | cobalt_info("timings %ux%u out of range\n",
| ^~~~~~~~~~~
drivers/media/pci/cobalt/cobalt-driver.h:160:45: note: each undeclared identifier is reported only once for each function it appears in
160 | #define cobalt_info(fmt, arg...) v4l2_info(&cobalt->v4l2_dev, fmt, ## arg)
| ^~~~~~
include/linux/printk.h:483:33: note: in definition of macro 'printk_index_wrap'
483 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/media/v4l2-common.h:58:9: note: in expansion of macro 'printk'
58 | printk(level "%s: " fmt, (dev)->name , ## arg)
| ^~~~~~
include/media/v4l2-common.h:67:9: note: in expansion of macro 'v4l2_printk'
67 | v4l2_printk(KERN_INFO, dev, fmt , ## arg)
| ^~~~~~~~~~~
drivers/media/pci/cobalt/cobalt-driver.h:160:34: note: in expansion of macro 'v4l2_info'
160 | #define cobalt_info(fmt, arg...) v4l2_info(&cobalt->v4l2_dev, fmt, ## arg)
| ^~~~~~~~~
drivers/media/pci/cobalt/cobalt-v4l2.c:635:17: note: in expansion of macro 'cobalt_info'
635 | cobalt_info("timings %ux%u out of range\n",
| ^~~~~~~~~~~
vim +/cobalt +160 drivers/media/pci/cobalt/cobalt-driver.h
85756a069c55e0 Hans Verkuil 2015-05-12 157
85756a069c55e0 Hans Verkuil 2015-05-12 158 #define cobalt_err(fmt, arg...) v4l2_err(&cobalt->v4l2_dev, fmt, ## arg)
85756a069c55e0 Hans Verkuil 2015-05-12 159 #define cobalt_warn(fmt, arg...) v4l2_warn(&cobalt->v4l2_dev, fmt, ## arg)
85756a069c55e0 Hans Verkuil 2015-05-12 @160 #define cobalt_info(fmt, arg...) v4l2_info(&cobalt->v4l2_dev, fmt, ## arg)
85756a069c55e0 Hans Verkuil 2015-05-12 161 #define cobalt_dbg(level, fmt, arg...) \
85756a069c55e0 Hans Verkuil 2015-05-12 162 v4l2_dbg(level, cobalt_debug, &cobalt->v4l2_dev, fmt, ## arg)
85756a069c55e0 Hans Verkuil 2015-05-12 163
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-09-19 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 7:25 Guo Zihao
2026-09-18 23:34 ` kernel test robot
2026-09-19 1:51 ` kernel test robot [this message]
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=202609190912.ouKMS0Bi-lkp@intel.com \
--to=lkp@intel.com \
--cc=guozh23@xiaopeng.com \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=liuc63@xiaopeng.com \
--cc=mchehab@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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®