RE: Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)

RE: Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)

[Kostya Porotchkin]

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>

Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)

[Randy Dunlap]

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

Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)

[Randy Dunlap]

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

Re: linux-next: Tree for Mar 31 (drivers/phy/marvell/phy-mvebu-cp110-utmi.o)

[Randy Dunlap]

[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]

On 3/31/21 2:43 AM, Stephen Rothwell wrote:
> Hi all,
> 
> News: there will be no linux-next release on Friday or the following
> Monday.
> 
> Changes since 20210330:
> 
> The risc-v tree gained a conflict against Linus' tree.
> 
> The amdgpu tree lost its build failure.
> 
> The staging tree gained a conflict against the scmi tree.
> 
> Non-merge commits (relative to Linus' tree): 8070
>  7884 files changed, 461929 insertions(+), 205606 deletions(-)
> 
> ----------------------------------------------------------------------------
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" and checkout or reset to the new
> master.
> 
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log
> files in the Next directory.  Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig and htmldocs. And finally, a simple boot test
> of the powerpc pseries_le_defconfig kernel in qemu (with and without
> kvm enabled).
> 
> Below is a summary of the state of the merge.
> 
> I am currently merging 335 trees (counting Linus' and 87 trees of bug
> fix patches pending for the current merge release).
> 
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
> 
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
> 
> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
> Gortmaker for triage and bug fixes.
> 

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'


Full randconfig file is attached.

-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>

[-- Attachment #2: config-r8542.gz --]
[-- Type: application/gzip, Size: 33697 bytes --]