Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* RE: Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)
@ 2021-04-01 12:33 Kostya Porotchkin
  2021-04-01 16:29 ` Randy Dunlap
  0 siblings, 1 reply; 3+ messages in thread
From: Kostya Porotchkin @ 2021-04-01 12:33 UTC (permalink / raw)
  To: Randy Dunlap, Stephen Rothwell, Linux Next Mailing List
  Cc: Linux Kernel Mailing List, netdev

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?

Regards
Kosta
> 
> Full randconfig file is attached.
> 
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)
  2021-04-01 12:33 Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o) Kostya Porotchkin
@ 2021-04-01 16:29 ` Randy Dunlap
  2021-04-01 16:35   ` Randy Dunlap
  0 siblings, 1 reply; 3+ messages in thread
From: Randy Dunlap @ 2021-04-01 16:29 UTC (permalink / raw)
  To: Kostya Porotchkin, Stephen Rothwell, Linux Next Mailing List
  Cc: Linux Kernel Mailing List, netdev

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.
>>
>> --


-- 
~Randy


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)
  2021-04-01 16:29 ` Randy Dunlap
@ 2021-04-01 16:35   ` Randy Dunlap
  0 siblings, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2021-04-01 16:35 UTC (permalink / raw)
  To: Kostya Porotchkin, Stephen Rothwell, Linux Next Mailing List
  Cc: Linux Kernel Mailing List, netdev

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-01 12:33 Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o) Kostya Porotchkin
2021-04-01 16:29 ` Randy Dunlap
2021-04-01 16:35   ` Randy Dunlap

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git