From: kernel test robot <lkp@intel.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, Jessica Zhang <quic_jesszhan@quicinc.com>
Subject: [linux-next:master 1448/1841] drivers/gpu/drm/panel/panel-visionox-rm69299.c:241:42: sparse: sparse: symbol 'visionox_rm69299_1080p_display_desc' was not declared. Should it be static?
Date: Thu, 12 Jun 2025 00:06:05 +0800 [thread overview]
Message-ID: <202506120036.oCLAYYbS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 19a60293b9925080d97f22f122aca3fc46dadaf9
commit: 01a2c6756bcae987472228c41319fc6ab2cc89c8 [1448/1841] drm/panel: visionox-rm69299: add plumbing to support panel variants
config: i386-randconfig-063-20250611 (https://download.01.org/0day-ci/archive/20250612/202506120036.oCLAYYbS-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250612/202506120036.oCLAYYbS-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/202506120036.oCLAYYbS-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/panel/panel-visionox-rm69299.c:241:42: sparse: sparse: symbol 'visionox_rm69299_1080p_display_desc' was not declared. Should it be static?
vim +/visionox_rm69299_1080p_display_desc +241 drivers/gpu/drm/panel/panel-visionox-rm69299.c
240
> 241 const struct visionox_rm69299_panel_desc visionox_rm69299_1080p_display_desc = {
242 .mode = &visionox_rm69299_1080x2248_60hz,
243 .init_seq = (const u8 *)visionox_rm69299_1080x2248_60hz_init_seq,
244 .init_seq_len = ARRAY_SIZE(visionox_rm69299_1080x2248_60hz_init_seq),
245 };
246
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-11 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202506120036.oCLAYYbS-lkp@intel.com \
--to=lkp@intel.com \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_jesszhan@quicinc.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.