netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jonathan Lemon <jonathan.lemon@gmail.com>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	kernel-team@fb.com, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Lasse Johnsen <l@ssejohnsen.me>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH net-next v8 2/3] net: phy: broadcom: Add PTP support for some Broadcom PHYs.
Date: Sat, 18 Jun 2022 17:48:46 +0800	[thread overview]
Message-ID: <202206181756.RQjX7jiS-lkp@intel.com> (raw)
In-Reply-To: <20220616195218.217408-3-jonathan.lemon@gmail.com>

Hi Jonathan,

I love your patch! Yet something to improve:

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

url:    https://github.com/intel-lab-lkp/linux/commits/Jonathan-Lemon/Broadcom-PTP-PHY-support/20220617-035307
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 5dcb50c009c9f8ec1cfca6a81a05c0060a5bbf68
config: hexagon-randconfig-r016-20220617 (https://download.01.org/0day-ci/archive/20220618/202206181756.RQjX7jiS-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 91688716ba49942051dccdf7b9c4f81a7ec8feaf)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel-lab-lkp/linux/commit/8eadce9504aa8672818c2f8ebedb0a807a2608ac
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Jonathan-Lemon/Broadcom-PTP-PHY-support/20220617-035307
        git checkout 8eadce9504aa8672818c2f8ebedb0a807a2608ac
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> ld.lld: error: undefined symbol: ptp_cancel_worker_sync
   >>> referenced by bcm-phy-ptp.c:650 (drivers/net/phy/bcm-phy-ptp.c:650)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_stop) in archive drivers/built-in.a
   >>> referenced by bcm-phy-ptp.c:650 (drivers/net/phy/bcm-phy-ptp.c:650)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_stop) in archive drivers/built-in.a
   >>> referenced by bcm-phy-ptp.c:618 (drivers/net/phy/bcm-phy-ptp.c:618)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_hwtstamp) in archive drivers/built-in.a
   >>> referenced 1 more times
--
>> ld.lld: error: undefined symbol: ptp_clock_register
   >>> referenced by bcm-phy-ptp.c:706 (drivers/net/phy/bcm-phy-ptp.c:706)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_probe) in archive drivers/built-in.a
   >>> referenced by bcm-phy-ptp.c:706 (drivers/net/phy/bcm-phy-ptp.c:706)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_probe) in archive drivers/built-in.a
--
>> ld.lld: error: undefined symbol: ptp_schedule_worker
   >>> referenced by bcm-phy-ptp.c:554 (drivers/net/phy/bcm-phy-ptp.c:554)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_txtstamp) in archive drivers/built-in.a
   >>> referenced by bcm-phy-ptp.c:554 (drivers/net/phy/bcm-phy-ptp.c:554)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_txtstamp) in archive drivers/built-in.a
--
>> ld.lld: error: undefined symbol: ptp_clock_index
   >>> referenced by bcm-phy-ptp.c:631 (drivers/net/phy/bcm-phy-ptp.c:631)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_ts_info) in archive drivers/built-in.a
   >>> referenced by bcm-phy-ptp.c:631 (drivers/net/phy/bcm-phy-ptp.c:631)
   >>> net/phy/bcm-phy-ptp.o:(bcm_ptp_ts_info) in archive drivers/built-in.a

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for BCM_NET_PHYPTP
   Depends on NETDEVICES && PHYLIB && PTP_1588_CLOCK_OPTIONAL
   Selected by
   - BROADCOM_PHY && NETDEVICES && PHYLIB && NETWORK_PHY_TIMESTAMPING

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  reply	other threads:[~2022-06-18  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 19:52 [PATCH net-next v8 0/3] Broadcom PTP PHY support Jonathan Lemon
2022-06-16 19:52 ` [PATCH net-next v8 1/3] net: phy: broadcom: Add Broadcom PTP hooks to bcm-phy-lib Jonathan Lemon
2022-06-16 19:52 ` [PATCH net-next v8 2/3] net: phy: broadcom: Add PTP support for some Broadcom PHYs Jonathan Lemon
2022-06-18  9:48   ` kernel test robot [this message]
2022-06-20 22:45     ` Jonathan Lemon
2022-06-16 19:52 ` [PATCH net-next v8 3/3] net: phy: Add support for 1PPS out and external timestamps Jonathan Lemon

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=202206181756.RQjX7jiS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel-team@fb.com \
    --cc=kuba@kernel.org \
    --cc=l@ssejohnsen.me \
    --cc=linux@armlinux.org.uk \
    --cc=llvm@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.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;
as well as URLs for NNTP newsgroup(s).