From: Arnd Bergmann <arnd@arndb.de>
To: kernel-build-reports@lists.linaro.org
Cc: "Olof's autobuilder" <build@lixom.net>,
olof@lixom.net, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: mainline build: 2 warnings 2 failures (mainline/v4.7-8076-g7a66ecf)
Date: Mon, 01 Aug 2016 14:54:46 +0200 [thread overview]
Message-ID: <1718455.kHldGdgFKM@wuerfel> (raw)
In-Reply-To: <579f414c.1590620a.baeb.02ce@mx.google.com>
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
parent reply other threads:[~2016-08-01 13:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <579f414c.1590620a.baeb.02ce@mx.google.com>]
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=1718455.kHldGdgFKM@wuerfel \
--to=arnd@arndb.de \
--cc=build@lixom.net \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®