From: kernel test robot <lkp@intel.com>
To: Dongcheng Yan <dongcheng.yan@intel.com>,
linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl,
ricardo.ribalda@gmail.com, bingbu.cao@linux.intel.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
tomi.valkeinen@ideasonboard.com, jacopo.mondi@ideasonboard.com,
daxing.li@intel.com, dongcheng.yan@linux.intel.com,
ong.hock.yu@intel.com, balamurugan.c@intel.com,
wei.a.fu@intel.com
Subject: Re: [PATCH v5] media: i2c: add lt6911uxe hdmi bridge driver
Date: Mon, 10 Feb 2025 20:31:44 +0800 [thread overview]
Message-ID: <202502102022.iul448ho-lkp@intel.com> (raw)
In-Reply-To: <20250210060923.2434047-1-dongcheng.yan@intel.com>
Hi Dongcheng,
kernel test robot noticed the following build errors:
[auto build test ERROR on 2f87d0916ce0d2925cedbc9e8f5d6291ba2ac7b2]
url: https://github.com/intel-lab-lkp/linux/commits/Dongcheng-Yan/media-i2c-add-lt6911uxe-hdmi-bridge-driver/20250210-141140
base: 2f87d0916ce0d2925cedbc9e8f5d6291ba2ac7b2
patch link: https://lore.kernel.org/r/20250210060923.2434047-1-dongcheng.yan%40intel.com
patch subject: [PATCH v5] media: i2c: add lt6911uxe hdmi bridge driver
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20250210/202502102022.iul448ho-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250210/202502102022.iul448ho-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/202502102022.iul448ho-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/media/i2c/lt6911uxe.c:46:2: error: initialization of non-aggregate type '__u32' (aka 'unsigned int') with a designated initializer list
46 | V4L2_INIT_BT_TIMINGS(
| ^~~~~~~~~~~~~~~~~~~~~
47 | 160, 3840, /* min/max width */
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
48 | 120, 2160, /* min/max height */
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
49 | 50000000, 594000000, /* min/max pixelclock */
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
50 | V4L2_DV_BT_STD_CEA861 | V4L2_DV_BT_STD_DMT |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
51 | V4L2_DV_BT_STD_CVT,
| ~~~~~~~~~~~~~~~~~~~
52 | V4L2_DV_BT_CAP_PROGRESSIVE | V4L2_DV_BT_CAP_CUSTOM |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
53 | V4L2_DV_BT_CAP_REDUCED_BLANKING)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/uapi/linux/v4l2-dv-timings.h:17:2: note: expanded from macro 'V4L2_INIT_BT_TIMINGS'
17 | { .bt = { _width , ## args } }
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/media/i2c/lt6911uxe.c:444:7: error: no member named 'link_freq' in 'struct v4l2_mbus_config'
444 | cfg->link_freq = lt6911uxe->cur_mode.link_freq;
| ~~~ ^
2 errors generated.
vim +46 drivers/media/i2c/lt6911uxe.c
42
43 static const struct v4l2_dv_timings_cap lt6911uxe_timings_cap_4kp30 = {
44 .type = V4L2_DV_BT_656_1120,
45 /* Pixel clock from REF_01 p. 20. Min/max height/width are unknown */
> 46 V4L2_INIT_BT_TIMINGS(
47 160, 3840, /* min/max width */
48 120, 2160, /* min/max height */
49 50000000, 594000000, /* min/max pixelclock */
50 V4L2_DV_BT_STD_CEA861 | V4L2_DV_BT_STD_DMT |
51 V4L2_DV_BT_STD_CVT,
52 V4L2_DV_BT_CAP_PROGRESSIVE | V4L2_DV_BT_CAP_CUSTOM |
53 V4L2_DV_BT_CAP_REDUCED_BLANKING)
54 };
55
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-10 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 6:09 [PATCH v5] media: i2c: add lt6911uxe hdmi bridge driver Dongcheng Yan
2025-02-10 8:59 ` Yan, Dongcheng
2025-02-10 12:31 ` kernel test robot [this message]
2025-02-10 13:58 ` kernel test robot
2025-02-10 19:45 ` kernel test robot
2025-02-26 10:51 ` Hans Verkuil
2025-02-26 11:34 ` Sakari Ailus
2025-02-26 11:36 ` Sakari Ailus
2025-02-27 9:04 ` Yan, Dongcheng
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=202502102022.iul448ho-lkp@intel.com \
--to=lkp@intel.com \
--cc=balamurugan.c@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=daxing.li@intel.com \
--cc=dongcheng.yan@intel.com \
--cc=dongcheng.yan@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ong.hock.yu@intel.com \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wei.a.fu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox