From: kernel test robot <lkp@intel.com>
To: Dongcheng Yan <dongcheng.yan@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, "sys_oak" <sys_oak@intel.com>
Subject: [intel-lts:6.18/linux 1/1] drivers/media/i2c/max9x/max9296.c:35:5: sparse: sparse: symbol 'max9296_serial_link_timeout_ms' was not declared. Should it be static?
Date: Thu, 09 Jul 2026 15:27:54 +0800 [thread overview]
Message-ID: <202607091552.a2uOdoXc-lkp@intel.com> (raw)
Hi Dongcheng,
First bad commit (maybe != root cause):
tree: https://github.com/intel/linux-intel-lts.git 6.18/linux
head: 5100e1c74efeba843945492f8d5840e6166c0392
commit: baa76709460c288499d118e2daa55ca3df5a6436 [1/1] media: i2c: add gmsl & isx031 support
config: x86_64-randconfig-r113-20260708 (https://download.01.org/0day-ci/archive/20260709/202607091552.a2uOdoXc-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260709/202607091552.a2uOdoXc-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/202607091552.a2uOdoXc-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/media/i2c/max9x/max9296.c:35:5: sparse: sparse: symbol 'max9296_serial_link_timeout_ms' was not declared. Should it be static?
--
>> drivers/media/i2c/max9x/max96724.c:37:5: sparse: sparse: symbol 'max96724_serial_link_timeout_ms' was not declared. Should it be static?
vim +/max9296_serial_link_timeout_ms +35 drivers/media/i2c/max9x/max9296.c
2445b17eae1d53 Shahidan, Muhammad Shahmil 2026-04-08 33
2445b17eae1d53 Shahidan, Muhammad Shahmil 2026-04-08 34 // Params
2445b17eae1d53 Shahidan, Muhammad Shahmil 2026-04-08 @35 int max9296_serial_link_timeout_ms = MAX9296_DEFAULT_SERIAL_LINK_TIMEOUT_MS;
2445b17eae1d53 Shahidan, Muhammad Shahmil 2026-04-08 36 module_param(max9296_serial_link_timeout_ms, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
2445b17eae1d53 Shahidan, Muhammad Shahmil 2026-04-08 37 MODULE_PARM_DESC(max9296_serial_link_timeout_ms, "Timeout for serial link in milliseconds");
2445b17eae1d53 Shahidan, Muhammad Shahmil 2026-04-08 38
:::::: The code at line 35 was first introduced by commit
:::::: 2445b17eae1d5356936a0a598940dfaad469c29d Add serdes drivers
:::::: TO: Shahidan, Muhammad Shahmil <muhammad.shahmil.shahidan@intel.com>
:::::: CC: sys_oak <sys_oak@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-09 7:28 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=202607091552.a2uOdoXc-lkp@intel.com \
--to=lkp@intel.com \
--cc=dongcheng.yan@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sys_oak@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 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.