[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO6PR18MB4417A9BE44A8879928B0D0A7CA7B9@CO6PR18MB4417.namprd18.prod.outlook.com>
Date: Thu, 1 Apr 2021 12:33:11 +0000
From: Kostya Porotchkin <kostap@...vell.com>
To: Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Re: linux-next: Tree for Mar 31
(drivers/phy/marvell/phy-mvebu-cp110-utmi.o)
Hi, Randy,
> -----Original Message-----
> From: Randy Dunlap <rdunlap@...radead.org>
> Sent: Wednesday, March 31, 2021 18:28
> To: Stephen Rothwell <sfr@...b.auug.org.au>; Linux Next Mailing List <linux-
> next@...r.kernel.org>
> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>; Kostya
> Porotchkin <kostap@...vell.com>; netdev@...r.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?
Regards
Kosta
>
> Full randconfig file is attached.
>
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@...radead.org>
Powered by blists - more mailing lists