From: kernel test robot <lkp@intel.com>
To: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [bod:qcom-laptops-v6.18-rc4-camss-icp-bps-ipe-icp-boots+stats-b4 93/121] drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:439:34: sparse: sparse: symbol 'phy_qcom_mipi_csi2_ops_3ph_1_0' was not declared. Should it be static?
Date: Thu, 09 Jul 2026 12:38:15 +0800 [thread overview]
Message-ID: <202607091248.rf8X2HoK-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bod/linux.git qcom-laptops-v6.18-rc4-camss-icp-bps-ipe-icp-boots+stats-b4
head: ebd1e440443121d18f730ab2aeea5586a754f36f
commit: d7952be2f35aa9609bdcb72055e2410f4754a056 [93/121] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver
config: arc-randconfig-r134-20260709 (https://download.01.org/0day-ci/archive/20260709/202607091248.rf8X2HoK-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 16.1.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260709/202607091248.rf8X2HoK-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/202607091248.rf8X2HoK-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:439:34: sparse: sparse: symbol 'phy_qcom_mipi_csi2_ops_3ph_1_0' was not declared. Should it be static?
>> drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:449:36: sparse: sparse: symbol 'dphy_4nm_x1e_csiphy' was not declared. Should it be static?
>> drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c:456:36: sparse: sparse: symbol 'dphy_4nm_x1e_csiphy_timer' was not declared. Should it be static?
vim +/phy_qcom_mipi_csi2_ops_3ph_1_0 +439 drivers/phy/qualcomm/phy-qcom-mipi-csi2-3ph-dphy.c
438
> 439 const struct mipi_csi2phy_hw_ops phy_qcom_mipi_csi2_ops_3ph_1_0 = {
440 .hw_version_read = phy_qcom_mipi_csi2_hw_version_read,
441 .reset = phy_qcom_mipi_csi2_reset,
442 .lanes_enable = phy_qcom_mipi_csi2_lanes_enable,
443 .lanes_disable = phy_qcom_mipi_csi2_lanes_disable,
444 .isr = phy_qcom_mipi_csi2_isr,
445 };
446
447 const struct mipi_csi2phy_clk_freq zero = { 0 };
448
> 449 const struct mipi_csi2phy_clk_freq dphy_4nm_x1e_csiphy = {
450 .freq = {
451 300000000, 400000000, 480000000
452 },
453 .num_freq = 3,
454 };
455
> 456 const struct mipi_csi2phy_clk_freq dphy_4nm_x1e_csiphy_timer = {
457 .freq = {
458 266666667, 400000000
459 },
460 .num_freq = 2,
461 };
462
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-09 4:38 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=202607091248.rf8X2HoK-lkp@intel.com \
--to=lkp@intel.com \
--cc=bryan.odonoghue@linaro.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 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.