linux-kernel - Re: mainline build: 2 warnings 2 failures (mainline/v4.7-8076-g7a66ecf)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 01 Aug 2016 14:54:46 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	kernel-build-reports@...ts.linaro.org
Cc:	Olof's autobuilder <build@...om.net>, olof@...om.net,
	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org
Subject: Re: mainline build: 2 warnings 2 failures (mainline/v4.7-8076-g7a66ecf)

On Monday, August 1, 2016 5:32:12 AM CEST Olof's autobuilder wrote:

>         Runtime:                57m 10s
> 
>         Passed:                 121
>         Failed:                 2
> 
>         Warnings:               2
> 
>         Section mismatches:     0

Nice!

> Errors:
> 
>         arm64.allmodconfig:
> binder.c:(.text+0x2e1578): undefined reference to `usb_ep_set_maxpacket_limit'
> binder.c:(.text+0x2e1660): undefined reference to `usb_ep_set_maxpacket_limit'
> 
>         arm.allmodconfig:
> binder.c:(.text+0x209f70): undefined reference to `usb_ep_set_maxpacket_limit'
> binder.c:(.text+0x20a038): undefined reference to `usb_ep_set_maxpacket_limit'

This is fixed in linux-next by 0bf048abeb ("staging: emxx_udc: allow modular
build"), currently this is in the usb-next branch.

> Warnings:
>       1 arch/arm/mach-s3c64xx/common.h:27:30: warning: 'struct device_node' declared inside parameter list will not be visible outside of this definition or declaration

The workaround is in arm-soc, should be merged in the next few days

>       1 drivers/tty/serial/8250/8250_fintek.c:34:0: warning: "IRQ_MODE" redefined

I sent "8250/fintek: rename IRQ_MODE macro" on June 27, but Greg hasn't applied
it yet. It's currently the only remaining warning reported by Olof's build
bot for linux-next.

	Arnd