From: kernel test robot <lkp@intel.com>
To: Shengyang Chen <shengyang.chen@starfivetech.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>,
Changhuang Liang <changhuang.liang@starfivetech.com>
Subject: drivers/phy/starfive/phy-jh7110-dphy-tx.c:178: warning: Cannot understand * @maps:
Date: Sat, 26 Apr 2025 18:15:33 +0800 [thread overview]
Message-ID: <202504261831.YcGFqEO5-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 02ddfb981de88a2c15621115dd7be2431252c568
commit: d3ab7955330843699cdcc413edd7993923e6c016 phy: starfive: Add mipi dphy tx support
date: 11 months ago
config: riscv-randconfig-001-20250426 (https://download.01.org/0day-ci/archive/20250426/202504261831.YcGFqEO5-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250426/202504261831.YcGFqEO5-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/202504261831.YcGFqEO5-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/phy/starfive/phy-jh7110-dphy-tx.c:178: warning: Cannot understand * @maps:
on line 178 - I thought it was a doc line
vim +178 drivers/phy/starfive/phy-jh7110-dphy-tx.c
175
176 struct stf_dphy_info {
177 /**
> 178 * @maps:
179 *
180 * Physical lanes and logic lanes mapping table.
181 *
182 * The default order is:
183 * [data lane 0, data lane 1, data lane 2, date lane 3, clk lane]
184 */
185 u8 maps[STF_MAP_LANES_NUM];
186 };
187
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-26 10:15 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=202504261831.YcGFqEO5-lkp@intel.com \
--to=lkp@intel.com \
--cc=changhuang.liang@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shengyang.chen@starfivetech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox