From: kernel test robot <lkp@intel.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: oe-kbuild-all@lists.linux.dev, Vinod Koul <vkoul@kernel.org>,
Kishon <kishon@ti.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Subject: [phy:next 4/30] drivers/phy/mediatek/phy-mtk-dp.c:168:2-3: Unneeded semicolon
Date: Tue, 15 Sep 2026 18:26:58 +0200 [thread overview]
Message-ID: <202609151827.yVAIUqNq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git next
head: 8bc74189b12e3d094d45eb82946c1fa17569fc93
commit: 3b7c0d1a2314a44f71003c196afa4f33c51e5067 [4/30] phy: phy-mtk-dp: Migrate register offsets to SoC specific pdata
config: m68k-randconfig-r052-20260915 (https://download.01.org/0day-ci/archive/20260915/202609151827.yVAIUqNq-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 8.5.0
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/202609151827.yVAIUqNq-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/phy/mediatek/phy-mtk-dp.c:168:2-3: Unneeded semicolon
vim +168 drivers/phy/mediatek/phy-mtk-dp.c
137
138 static int mtk_dp_phy_init(struct phy *phy)
139 {
140 struct mtk_dp_phy *dp_phy = phy_get_drvdata(phy);
141 const struct mtk_dp_phy_pdata *pdata = dp_phy->pdata;
142 const u32 reg = pdata->regs_dig_lane[DP_PHYD_LAN_DRIVING_PARAM_0];
143 static const u32 driving_params[] = {
144 DRIVING_PARAM_0_DEFAULT,
145 DRIVING_PARAM_1_DEFAULT,
146 DRIVING_PARAM_2_DEFAULT,
147 DRIVING_PARAM_3_DEFAULT,
148 DRIVING_PARAM_4_DEFAULT,
149 DRIVING_PARAM_5_DEFAULT,
150 DRIVING_PARAM_6_DEFAULT,
151 DRIVING_PARAM_7_DEFAULT,
152 DRIVING_PARAM_8_DEFAULT
153 };
154 int i, ret;
155
156 /*
157 * Assume that all lanes need the same driving parameters: this
158 * will bulk write from DRIVING_PARAM_0 to DRIVING_PARAM_8 on
159 * all lanes (a grand total of [9 * num_lanes] 32-bit writes)
160 */
161 for (i = 0; i < MTK_DP_PHY_MAX_LANES; i++) {
162 ret = regmap_bulk_write(dp_phy->regmap,
163 pdata->off_dig_lane[i] + reg,
164 driving_params,
165 ARRAY_SIZE(driving_params));
166 if (ret)
167 return ret;
> 168 };
169
170 return 0;
171 }
172
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-15 16:27 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=202609151827.yVAIUqNq-lkp@intel.com \
--to=lkp@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=kishon@ti.com \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkoul@kernel.org \
/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.