All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH net-next v3 01/13] net: phy: Introduce ethernet link topology representation
Date: Tue, 5 Dec 2023 23:31:07 +0800	[thread overview]
Message-ID: <202312052307.KuiFEyDS-lkp@intel.com> (raw)
In-Reply-To: <20231201163704.1306431-2-maxime.chevallier@bootlin.com>

Hi Maxime,

[This is a private test report for your RFC patch.]
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/Maxime-Chevallier/net-phy-Introduce-ethernet-link-topology-representation/20231202-003935
base:   net-next/main
patch link:    https://lore.kernel.org/r/20231201163704.1306431-2-maxime.chevallier%40bootlin.com
patch subject: [RFC PATCH net-next v3 01/13] net: phy: Introduce ethernet link topology representation
config: i386-randconfig-011-20231203 (https://download.01.org/0day-ci/archive/20231205/202312052307.KuiFEyDS-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231205/202312052307.KuiFEyDS-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/202312052307.KuiFEyDS-lkp@intel.com/

All errors (new ones prefixed by >>):

>> ld.lld: error: undefined symbol: phy_link_topo_init
   >>> referenced by dev.c:10836 (net/core/dev.c:10836)
   >>>               net/core/dev.o:(alloc_netdev_mqs) in archive vmlinux.a

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for DRM_I915_DEBUG_GEM
   Depends on [n]: HAS_IOMEM [=y] && DRM_I915 [=m] && EXPERT [=y] && DRM_I915_WERROR [=n]
   Selected by [m]:
   - DRM_I915_DEBUG [=y] && HAS_IOMEM [=y] && DRM_I915 [=m] && EXPERT [=y] && !COMPILE_TEST [=n]

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

  parent reply	other threads:[~2023-12-05 15:31 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 16:36 [RFC PATCH net-next v3 00/13] Introduce PHY listing and link_topology tracking Maxime Chevallier
2023-12-01 16:36 ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 01/13] net: phy: Introduce ethernet link topology representation Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-05 14:49   ` kernel test robot
2023-12-05 15:31   ` kernel test robot [this message]
2023-12-09 17:02   ` Simon Horman
2023-12-09 17:02     ` Simon Horman
2023-12-11 11:06     ` Maxime Chevallier
2023-12-11 11:06       ` Maxime Chevallier
2023-12-11 14:09       ` Andrew Lunn
2023-12-11 14:09         ` Andrew Lunn
2023-12-12 13:10         ` Maxime Chevallier
2023-12-12 13:10           ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 02/13] net: sfp: pass the phy_device when disconnecting an sfp module's PHY Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 03/13] net: phy: add helpers to handle sfp phy connect/disconnect Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 04/13] net: sfp: Add helper to return the SFP bus name Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 05/13] net: ethtool: Allow passing a phy index for some commands Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-05 16:35   ` kernel test robot
2023-12-01 16:36 ` [RFC PATCH net-next v3 06/13] netlink: specs: add phy-index as a header parameter Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-04 10:36   ` Maxime Chevallier
2023-12-04 10:36     ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 07/13] net: ethtool: Introduce a command to list PHYs on an interface Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-09 17:04   ` Simon Horman
2023-12-09 17:04     ` Simon Horman
2023-12-11 11:07     ` Maxime Chevallier
2023-12-11 11:07       ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 08/13] netlink: specs: add ethnl PHY_GET command set Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-04 10:37   ` Maxime Chevallier
2023-12-04 10:37     ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 09/13] net: ethtool: plca: Target the command to the requested PHY Maxime Chevallier
2023-12-01 16:36   ` Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 10/13] net: ethtool: pse-pd: " Maxime Chevallier
2023-12-01 16:37   ` Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 11/13] net: ethtool: cable-test: " Maxime Chevallier
2023-12-01 16:37   ` Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 12/13] net: ethtool: strset: Allow querying phy stats by index Maxime Chevallier
2023-12-01 16:37   ` Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 13/13] Documentation: networking: document phy_link_topology Maxime Chevallier
2023-12-01 16:37   ` Maxime Chevallier

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=202312052307.KuiFEyDS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=maxime.chevallier@bootlin.com \
    --cc=oe-kbuild-all@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.