From: kernel test robot <lkp@intel.com>
To: Conor Dooley <conor.dooley@microchip.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Cc: kbuild-all@lists.01.org, Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
daire.mcnamara@microchip.com, lewis.hanly@microchip.com,
cyril.jean@microchip.com,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v2 3/4] riscv: select vitesse phy driver for polarfire soc
Date: Fri, 22 Apr 2022 08:18:38 +0800 [thread overview]
Message-ID: <202204220822.swSeha61-lkp@intel.com> (raw)
In-Reply-To: <20220421085805.1220195-4-conor.dooley@microchip.com>
Hi Conor,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.18-rc3 next-20220421]
[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]
url: https://github.com/intel-lab-lkp/linux/commits/Conor-Dooley/polarfire-soc-kconfig-maintainers-updates/20220421-172138
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git b253435746d9a4a701b5f09211b9c14d3370d0da
config: riscv-randconfig-r002-20220420 (https://download.01.org/0day-ci/archive/20220422/202204220822.swSeha61-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.0
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/dc055eafe9cad74b3b01bed537c6f1496cddabe4
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Conor-Dooley/polarfire-soc-kconfig-maintainers-updates/20220421-172138
git checkout dc055eafe9cad74b3b01bed537c6f1496cddabe4
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc8221_config_init':
>> vitesse.c:(.text+0x10): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc73xx_config_init':
vitesse.c:(.text+0x30): undefined reference to `mdiobus_write'
>> riscv64-linux-ld: vitesse.c:(.text+0x44): undefined reference to `phy_modify'
>> riscv64-linux-ld: vitesse.c:(.text+0x58): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x74): undefined reference to `phy_modify'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc739x_config_init':
vitesse.c:(.text+0x96): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0xaa): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0xc2): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0xda): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0xee): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x102): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x11a): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x130): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x142): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x156): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x16a): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x180): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x196): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x1ac): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x1bc): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x1d0): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x1e0): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x1f4): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc73xx_write_page':
>> vitesse.c:(.text+0x226): undefined reference to `__mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc73xx_read_page':
>> vitesse.c:(.text+0x238): undefined reference to `__mdiobus_read'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc738x_config_init':
vitesse.c:(.text+0x260): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x274): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x28c): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x2a4): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x2b8): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x2cc): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x2e4): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x2fa): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x30c): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x320): undefined reference to `mdiobus_write'
>> riscv64-linux-ld: vitesse.c:(.text+0x332): undefined reference to `mdiobus_read'
riscv64-linux-ld: vitesse.c:(.text+0x34e): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x362): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x378): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x38c): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x3a2): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x3b8): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x3ce): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o:vitesse.c:(.text+0x3e2): more undefined references to `mdiobus_write' follow
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc738x_config_init':
>> vitesse.c:(.text+0x438): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x44e): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x462): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x476): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x48c): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x4a2): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o:vitesse.c:(.text+0x4ba): more undefined references to `mdiobus_write' follow
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc738x_config_init':
vitesse.c:(.text+0x53a): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x54a): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x55e): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x56e): undefined reference to `phy_modify'
riscv64-linux-ld: vitesse.c:(.text+0x582): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc8601_config_init':
>> vitesse.c:(.text+0x5c4): undefined reference to `mdiobus_read'
riscv64-linux-ld: vitesse.c:(.text+0x5e4): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc82xx_config_intr':
vitesse.c:(.text+0x66c): undefined reference to `mdiobus_read'
riscv64-linux-ld: vitesse.c:(.text+0x68a): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc824x_config_init':
vitesse.c:(.text+0x6b8): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x6d8): undefined reference to `mdiobus_read'
riscv64-linux-ld: vitesse.c:(.text+0x70c): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `.L39':
vitesse.c:(.text+0x766): undefined reference to `mdiobus_read'
>> riscv64-linux-ld: vitesse.c:(.text+0x774): undefined reference to `phy_error'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `.L40':
>> vitesse.c:(.text+0x788): undefined reference to `phy_trigger_machine'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc82x4_config_aneg':
>> vitesse.c:(.text+0x7ca): undefined reference to `genphy_setup_forced'
riscv64-linux-ld: vitesse.c:(.text+0x7fa): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x814): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x832): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x850): undefined reference to `mdiobus_write'
riscv64-linux-ld: vitesse.c:(.text+0x876): undefined reference to `mdiobus_write'
riscv64-linux-ld: drivers/net/phy/vitesse.o:vitesse.c:(.text+0x88a): more undefined references to `mdiobus_write' follow
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `vsc82x4_config_aneg':
>> vitesse.c:(.text+0x8a4): undefined reference to `__genphy_config_aneg'
riscv64-linux-ld: drivers/net/phy/vitesse.o: in function `.L0 ':
>> vitesse.c:(.init.text+0xc): undefined reference to `phy_drivers_register'
>> riscv64-linux-ld: vitesse.c:(.exit.text+0xa): undefined reference to `phy_drivers_unregister'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for VITESSE_PHY
Depends on NETDEVICES && PHYLIB
Selected by
- SOC_MICROCHIP_POLARFIRE
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-04-22 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 8:58 [PATCH v2 0/4] polarfire soc kconfig/maintainers updates Conor Dooley
2022-04-21 8:58 ` [PATCH v2 1/4] riscv: select peripheral drivers for polarfire soc Conor Dooley
2022-04-21 8:58 ` [PATCH v2 2/4] riscv: config: enable the mailbox framework Conor Dooley
2022-04-21 8:58 ` [PATCH v2 3/4] riscv: select vitesse phy driver for polarfire soc Conor Dooley
2022-04-22 0:18 ` kernel test robot [this message]
2022-04-22 1:29 ` kernel test robot
2022-04-21 8:58 ` [PATCH v2 4/4] MAINTAINERS: add polarfire rng, pci and clock drivers Conor Dooley
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=202204220822.swSeha61-lkp@intel.com \
--to=lkp@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=kbuild-all@lists.01.org \
--cc=lewis.hanly@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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