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: Re: [PATCH net-next v14] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
Date: Wed, 2 Sep 2026 20:55:28 +0800	[thread overview]
Message-ID: <202609022033.agNeEqvg-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "linux-review patch is more than 7 days old, verify it wasn't already superseded"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260824025625.2688693-1-kyle.switch@motor-comm.com>
References: <20260824025625.2688693-1-kyle.switch@motor-comm.com>
TO: Kyle Switch <kyle.switch@motor-comm.com>
TO: Frank.Sae@motor-comm.com
TO: andrew@lunn.ch
TO: hkallweit1@gmail.com
TO: linux@armlinux.org.uk
TO: davem@davemloft.net
TO: edumazet@google.com
TO: kuba@kernel.org
TO: pabeni@redhat.com
TO: netdev@vger.kernel.org
TO: linux-kernel@vger.kernel.org
CC: ming.xu@motor-comm.com
CC: xiaolin.xu@motor-comm.com
CC: jianmin.wang@motor-comm.com
CC: jie.han@motor-comm.com

Hi Kyle,

kernel test robot noticed the following build errors:

[auto build test ERROR on net-next/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Kyle-Switch/net-phy-Add-driver-for-Motorcomm-Quad-2-5GbE-phy/20260824-105625
base:   net-next/main
patch link:    https://lore.kernel.org/r/20260824025625.2688693-1-kyle.switch%40motor-comm.com
patch subject: [PATCH net-next v14] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
:::::: branch date: 9 days ago
:::::: commit date: 9 days ago
config: x86_64-randconfig-075-20250806 (https://download.01.org/0day-ci/archive/20260902/202609022033.agNeEqvg-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260902/202609022033.agNeEqvg-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/202609022033.agNeEqvg-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: vmlinux.o: in function `ytphy_read_top_ext':
>> drivers/net/phy/motorcomm.c:481:(.text+0x2a8e6e5): undefined reference to `__phy_package_write'
>> ld: drivers/net/phy/motorcomm.c:485:(.text+0x2a8e708): undefined reference to `__phy_package_read'
   ld: vmlinux.o: in function `yt8824_probe':
>> drivers/net/phy/motorcomm.c:4569:(.text+0x2a8fc60): undefined reference to `devm_of_phy_package_join'
>> ld: drivers/net/phy/motorcomm.c:4573:(.text+0x2a8fca2): undefined reference to `phy_package_probe_once'
   ld: vmlinux.o: in function `yt8824_phy_package_probe_once':
>> drivers/net/phy/motorcomm.c:4530:(.text+0x2a8fcc0): undefined reference to `phy_package_get_priv'
>> ld: drivers/net/phy/motorcomm.c:4531:(.text+0x2a8fccb): undefined reference to `phy_package_get_node'
   ld: vmlinux.o: in function `ytphy_write_top_ext':
   drivers/net/phy/motorcomm.c:502:(.text+0x2a903a5): undefined reference to `__phy_package_write'
>> ld: drivers/net/phy/motorcomm.c:506:(.text+0x2a903cc): undefined reference to `__phy_package_write'
   ld: vmlinux.o: in function `yt8824_config_aneg':
   drivers/net/phy/motorcomm.c:4495:(.text+0x2a90794): undefined reference to `phy_package_get_priv'
   ld: vmlinux.o: in function `yt8824_aneg_done':
   drivers/net/phy/motorcomm.c:4205:(.text+0x2a90898): undefined reference to `phy_package_get_priv'
   ld: vmlinux.o: in function `yt8824_get_features':
   drivers/net/phy/motorcomm.c:4183:(.text+0x2a91254): undefined reference to `phy_package_get_priv'
   ld: vmlinux.o: in function `yt8824_read_status':
   drivers/net/phy/motorcomm.c:4289:(.text+0x2a912dc): undefined reference to `phy_package_get_priv'
   ld: vmlinux.o: in function `yt8824_soft_reset':
   drivers/net/phy/motorcomm.c:915:(.text+0x2a92a16): undefined reference to `phy_package_get_priv'
   ld: vmlinux.o:drivers/net/phy/motorcomm.c:4400: more undefined references to `phy_package_get_priv' follow


vim +481 drivers/net/phy/motorcomm.c

70479a40954cf3 Frank       2022-10-28  468  
7d5c6b4a2f233a Kyle Switch 2026-08-24  469  /**
7d5c6b4a2f233a Kyle Switch 2026-08-24  470   * ytphy_read_top_ext() - read a PHY's top extended register for YT8824
7d5c6b4a2f233a Kyle Switch 2026-08-24  471   * @phydev: a pointer to a &struct phy_device
7d5c6b4a2f233a Kyle Switch 2026-08-24  472   * @regnum: register number to read
7d5c6b4a2f233a Kyle Switch 2026-08-24  473   *
7d5c6b4a2f233a Kyle Switch 2026-08-24  474   * Returns: the value of regnum reg or negative error code
7d5c6b4a2f233a Kyle Switch 2026-08-24  475   */
7d5c6b4a2f233a Kyle Switch 2026-08-24  476  static int ytphy_read_top_ext(struct phy_device *phydev, u16 regnum)
7d5c6b4a2f233a Kyle Switch 2026-08-24  477  {
7d5c6b4a2f233a Kyle Switch 2026-08-24  478  	int ret;
7d5c6b4a2f233a Kyle Switch 2026-08-24  479  
7d5c6b4a2f233a Kyle Switch 2026-08-24  480  	lockdep_assert_held(&phydev->mdio.bus->mdio_lock);
7d5c6b4a2f233a Kyle Switch 2026-08-24 @481  	ret = __phy_package_write(phydev, 0, YTPHY_PAGE_SELECT, regnum);
7d5c6b4a2f233a Kyle Switch 2026-08-24  482  	if (ret < 0)
7d5c6b4a2f233a Kyle Switch 2026-08-24  483  		return ret;
7d5c6b4a2f233a Kyle Switch 2026-08-24  484  
7d5c6b4a2f233a Kyle Switch 2026-08-24 @485  	return __phy_package_read(phydev, 0, YTPHY_PAGE_DATA);
7d5c6b4a2f233a Kyle Switch 2026-08-24  486  }
7d5c6b4a2f233a Kyle Switch 2026-08-24  487  
7d5c6b4a2f233a Kyle Switch 2026-08-24  488  /**
7d5c6b4a2f233a Kyle Switch 2026-08-24  489   * ytphy_write_top_ext() - write a PHY's top extended register for YT8824
7d5c6b4a2f233a Kyle Switch 2026-08-24  490   * @phydev: a pointer to a &struct phy_device
7d5c6b4a2f233a Kyle Switch 2026-08-24  491   * @regnum: register number to write
7d5c6b4a2f233a Kyle Switch 2026-08-24  492   * @val: register val to write
7d5c6b4a2f233a Kyle Switch 2026-08-24  493   *
7d5c6b4a2f233a Kyle Switch 2026-08-24  494   * Returns: 0 or negative error code
7d5c6b4a2f233a Kyle Switch 2026-08-24  495   */
7d5c6b4a2f233a Kyle Switch 2026-08-24  496  static int ytphy_write_top_ext(struct phy_device *phydev, u16 regnum,
7d5c6b4a2f233a Kyle Switch 2026-08-24  497  			       u16 val)
7d5c6b4a2f233a Kyle Switch 2026-08-24  498  {
7d5c6b4a2f233a Kyle Switch 2026-08-24  499  	int ret;
7d5c6b4a2f233a Kyle Switch 2026-08-24  500  
7d5c6b4a2f233a Kyle Switch 2026-08-24  501  	lockdep_assert_held(&phydev->mdio.bus->mdio_lock);
7d5c6b4a2f233a Kyle Switch 2026-08-24  502  	ret = __phy_package_write(phydev, 0, YTPHY_PAGE_SELECT, regnum);
7d5c6b4a2f233a Kyle Switch 2026-08-24  503  	if (ret < 0)
7d5c6b4a2f233a Kyle Switch 2026-08-24  504  		return ret;
7d5c6b4a2f233a Kyle Switch 2026-08-24  505  
7d5c6b4a2f233a Kyle Switch 2026-08-24 @506  	return __phy_package_write(phydev, 0, YTPHY_PAGE_DATA, val);
7d5c6b4a2f233a Kyle Switch 2026-08-24  507  }
7d5c6b4a2f233a Kyle Switch 2026-08-24  508  

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

             reply	other threads:[~2026-09-02 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 12:55 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-24  2:56 [PATCH net-next v14] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-08-25  9:49 ` Paolo Abeni

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=202609022033.agNeEqvg-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.