[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b567ac02-c5b1-188e-1431-a903a2a00a34@infradead.org>
Date: Thu, 1 Apr 2021 09:29:06 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Kostya Porotchkin <kostap@...vell.com>,
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: linux-next: Tree for Mar 31
(drivers/phy/marvell/phy-mvebu-cp110-utmi.o)
On 4/1/21 5:33 AM, Kostya Porotchkin wrote:
> 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?
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.
>>
>> --
--
~Randy
Powered by blists - more mailing lists