From: kernel test robot <lkp@intel.com>
To: Kyle Switch <kyle.switch@motor-comm.com>,
Frank.Sae@motor-comm.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jianmin.wang@motor-comm.com,
ming.xu@motor-comm.com, xiaolin.xu@motor-comm.com,
jie.han@motor-comm.com
Subject: Re: [PATCH] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
Date: Wed, 5 Aug 2026 20:26:19 +0800 [thread overview]
Message-ID: <202608052037.5FzKDBji-lkp@intel.com> (raw)
In-Reply-To: <20260714111203.3852126-1-kyle.switch@motor-comm.com>
Hi Kyle,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net/main]
[also build test WARNING on linus/master v7.2-rc6 next-20260804]
[cannot apply to net-next/main]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kyle-Switch/net-phy-Add-driver-for-Motorcomm-Quad-2-5GbE-phy/20260805-175843
base: net/main
patch link: https://lore.kernel.org/r/20260714111203.3852126-1-kyle.switch%40motor-comm.com
patch subject: [PATCH] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
config: alpha-allmodconfig (https://download.01.org/0day-ci/archive/20260805/202608052037.5FzKDBji-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260805/202608052037.5FzKDBji-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/202608052037.5FzKDBji-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/net/phy/motorcomm.c:519 function parameter 'val' not described in 'ytphy_write_top_ext'
>> Warning: drivers/net/phy/motorcomm.c:3230 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* configuration YT8824 to one template test mode.
Warning: drivers/net/phy/motorcomm.c:3255 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* enable YT8824 serdes isolate.
Warning: drivers/net/phy/motorcomm.c:3284 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* do YT8824 UTP softreset.
Warning: drivers/net/phy/motorcomm.c:3321 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* disable YT8824 template test mode.
Warning: drivers/net/phy/motorcomm.c:3356 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* disable YT8824 serdes isolate.
Warning: drivers/net/phy/motorcomm.c:3464 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* external YT8824 init
Warning: drivers/net/phy/motorcomm.c:3933 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* internal YT8824 init
>> Warning: drivers/net/phy/motorcomm.c:4351 expecting prototype for yt8824_config_aneg(). Prototype was for yt8824_aneg_done() instead
>> Warning: drivers/net/phy/motorcomm.c:4380 function parameter 'status' not described in 'yt8824_read_status_paged'
>> Warning: drivers/net/phy/motorcomm.c:4380 function parameter 'lpa' not described in 'yt8824_read_status_paged'
>> Warning: drivers/net/phy/motorcomm.c:4454 function parameter 'reg_space' not described in 'yt8824_utp_power_on'
>> Warning: drivers/net/phy/motorcomm.c:4487 function parameter 'reg_space' not described in 'yt8824_utp_power_down'
>> Warning: drivers/net/phy/motorcomm.c:519 function parameter 'val' not described in 'ytphy_write_top_ext'
>> Warning: drivers/net/phy/motorcomm.c:4380 function parameter 'status' not described in 'yt8824_read_status_paged'
>> Warning: drivers/net/phy/motorcomm.c:4380 function parameter 'lpa' not described in 'yt8824_read_status_paged'
>> Warning: drivers/net/phy/motorcomm.c:4454 function parameter 'reg_space' not described in 'yt8824_utp_power_on'
>> Warning: drivers/net/phy/motorcomm.c:4487 function parameter 'reg_space' not described in 'yt8824_utp_power_down'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-08-05 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 11:12 [PATCH] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-07-14 21:43 ` Andrew Lunn
2026-07-15 11:56 ` Kyle Switch
2026-07-14 21:46 ` Andrew Lunn
2026-07-15 11:59 ` Kyle Switch
2026-07-15 13:09 ` Andrew Lunn
2026-07-17 3:47 ` Kyle Switch
2026-08-05 12:26 ` kernel test robot [this message]
2026-08-05 22:28 ` 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=202608052037.5FzKDBji-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jianmin.wang@motor-comm.com \
--cc=jie.han@motor-comm.com \
--cc=kuba@kernel.org \
--cc=kyle.switch@motor-comm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ming.xu@motor-comm.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=xiaolin.xu@motor-comm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox