All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [phy:next 5/31] drivers/phy/mediatek/phy-mtk-dp.c:334:10: sparse: sparse: missing braces around initializer
Date: Tue, 15 Sep 2026 07:40:47 +0800	[thread overview]
Message-ID: <202609150736.x8tGAimG-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: drivers/phy/mediatek/phy-mtk-dp.c:334:10: sparse: sparse: missing braces around initializer"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: Vinod Koul <vkoul@kernel.org>
CC: Kishon <kishon@ti.com>
TO: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
CC: Vinod Koul <vkoul@kernel.org>
CC: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git next
head:   d837aabce96ef6f4cc6b179e1055d8cdf85cfe38
commit: ae859204b519a384ad0136c21599bab9321090ce [5/31] phy: phy-mtk-dp: Migrate register offsets to SoC specific pdata
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: parisc-randconfig-r133-20260914 (https://download.01.org/0day-ci/archive/20260915/202609150736.x8tGAimG-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.4.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260915/202609150736.x8tGAimG-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/r/202609150736.x8tGAimG-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/phy/mediatek/phy-mtk-dp.c:334:10: sparse: sparse: missing braces around initializer
>> drivers/phy/mediatek/phy-mtk-dp.c:334:26: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned short @@     got unsigned short const * @@
   drivers/phy/mediatek/phy-mtk-dp.c:334:26: sparse:     expected unsigned short
   drivers/phy/mediatek/phy-mtk-dp.c:334:26: sparse:     got unsigned short const *

vim +334 drivers/phy/mediatek/phy-mtk-dp.c

6a23afad443a8e Markus Schneider-Pargmann  2022-06-24  331  
ae859204b519a3 AngeloGioacchino Del Regno 2026-09-10  332  static const struct mtk_dp_phy_pdata mt8195_dp_phy_data = {
ae859204b519a3 AngeloGioacchino Del Regno 2026-09-10  333  	.off_dig_glb = 0x1000,
ae859204b519a3 AngeloGioacchino Del Regno 2026-09-10 @334  	.off_dig_lane = (const u16[]) { 0x1100, 0x1200, 0x1300, 0x1400 },
ae859204b519a3 AngeloGioacchino Del Regno 2026-09-10  335  	.regs_dig_glb = mt8195_phy_dig_glb_regs,
ae859204b519a3 AngeloGioacchino Del Regno 2026-09-10  336  	.regs_dig_lane = mt8195_phy_dig_lane_regs,
ae859204b519a3 AngeloGioacchino Del Regno 2026-09-10  337  };
ae859204b519a3 AngeloGioacchino Del Regno 2026-09-10  338  

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-09-14 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 23:40 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-14 16:45 [phy:next 5/31] drivers/phy/mediatek/phy-mtk-dp.c:334:10: sparse: sparse: missing braces around initializer kernel test robot

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=202609150736.x8tGAimG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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.