Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Kostya Porotchkin <kostap@marvell.com>,
	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>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)
Date: Thu, 1 Apr 2021 09:35:04 -0700
Message-ID: <70a1d2ea-406c-c3f2-30a8-54ed3e95c646@infradead.org> (raw)
In-Reply-To: <b567ac02-c5b1-188e-1431-a903a2a00a34@infradead.org>

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


  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 12:33 Kostya Porotchkin
2021-04-01 16:29 ` Randy Dunlap
2021-04-01 16:35   ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-31  9:43 linux-next: Tree for Mar 31 Stephen Rothwell
2021-03-31 15:28 ` linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o) Randy Dunlap

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=70a1d2ea-406c-c3f2-30a8-54ed3e95c646@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=kostap@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

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