Messages in this thread | | | Subject | Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o) | From | Randy Dunlap <> | Date | Thu, 1 Apr 2021 09:35:04 -0700 |
| |
On 4/1/21 9:29 AM, Randy Dunlap wrote: > On 4/1/21 5:33 AM, Kostya Porotchkin wrote: >> Hi, Randy, >> >>> -----Original Message----- >>> From: Randy Dunlap <rdunlap@infradead.org> >>> Sent: Wednesday, March 31, 2021 18:28 >>> To: Stephen Rothwell <sfr@canb.auug.org.au>; Linux Next Mailing List <linux- >>> next@vger.kernel.org> >>> Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Kostya >>> Porotchkin <kostap@marvell.com>; netdev@vger.kernel.org >>> Subject: [EXT] Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu- >>> cp110-utmi.o) >>> >> >> >>> >>> on i386: >>> >>> ld: drivers/phy/marvell/phy-mvebu-cp110-utmi.o: in function >>> `mvebu_cp110_utmi_phy_probe': >>> phy-mvebu-cp110-utmi.c:(.text+0x152): undefined reference to >>> `of_usb_get_dr_mode_by_phy' >>> >> [KP] This driver depends on ARCH_MVEBU (arm64). >> How it happens that it is included in i386 builds? > > Due to COMPILE_TEST: > > config PHY_MVEBU_CP110_UTMI > tristate "Marvell CP110 UTMI driver" > depends on ARCH_MVEBU || COMPILE_TEST > depends on OF > select GENERIC_PHY > > >> >> Regards >> Kosta >>> >>> Full randconfig file is attached. >>> >>> --
This happens because CONFIG_USB is not set but the missing function is only compiled if CONFIG_USB_COMMON is set.
-- ~Randy
| |