On 5/27/21 12:57 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20210526:
> 
> The kvm-fixes tree gained another build failure so I used the version from
> next-20210524.
> 
> The hid tree (I think) gained a build failure that I left broken.
> 
> The amdgpu tree gained a build failure for which I reverted a commit.
> 
> The scsi-mkp tree gained a build failuer so I used the version from
> next-20210526.
> 
> Non-merge commits (relative to Linus' tree): 5002
>  4946 files changed, 230454 insertions(+), 77632 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 331 trees (counting Linus' and 89 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/usb/class/cdc-wdm.o: in function `wdm_disconnect':
cdc-wdm.c:(.text+0x7c5): undefined reference to `wwan_remove_port'
ld: drivers/usb/class/cdc-wdm.o: in function `wdm_in_callback':
cdc-wdm.c:(.text+0xb8d): undefined reference to `wwan_port_rx'
ld: drivers/usb/class/cdc-wdm.o: in function `wdm_create':
cdc-wdm.c:(.text+0x13af): undefined reference to `wwan_create_port'
ld: drivers/usb/class/cdc-wdm.o: in function `wdm_wwan_port_stop':
cdc-wdm.c:(.text+0x14b5): undefined reference to `wwan_port_get_drvdata'
ld: drivers/usb/class/cdc-wdm.o: in function `wdm_wwan_port_tx':
cdc-wdm.c:(.text+0x14ef): undefined reference to `wwan_port_get_drvdata'
ld: cdc-wdm.c:(.text+0x1571): undefined reference to `wwan_port_txoff'
ld: drivers/usb/class/cdc-wdm.o: in function `wdm_wwan_port_start':
cdc-wdm.c:(.text+0x1588): undefined reference to `wwan_port_get_drvdata'
ld: cdc-wdm.c:(.text+0x15c1): undefined reference to `wwan_port_txon'
ld: drivers/usb/class/cdc-wdm.o: in function `wdm_wwan_port_tx_complete':
cdc-wdm.c:(.text+0x1617): undefined reference to `wwan_port_txon'

Full randconfig file is attached.

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