From: Mark Brown <broonie@kernel•org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Magnus Damm <damm+renesas@opensource•se>,
Simon Horman <horms+renesas@verge•net.au>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-usb@vger•kernel.org
Subject: Re: next-20160705 build: 2 failures 6 warnings (next-20160705)
Date: Tue, 5 Jul 2016 11:52:42 +0200 [thread overview]
Message-ID: <20160705095242.GP6247@sirena.org.uk> (raw)
In-Reply-To: <E1bKMRb-0005l2-N2@optimist>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
On Tue, Jul 05, 2016 at 10:15:03AM +0100, Build bot for Mark Brown wrote:
For the past little while both arm and arm64 allmodconfig builds have
been failing with:
> drivers/built-in.o: In function `nbu2ss_drv_probe':
> binder.c:(.text+0x29438c): undefined reference to `usb_ep_set_maxpacket_limit'
> binder.c:(.text+0x294468): undefined reference to `usb_ep_set_maxpacket_limit'
That function is a static inline in linux/usb/gadget.h which does seem
to be included (the driver builds fine) so I'm not entirely sure why
this is failing - I've not had time to investigate properly, I don't
know if the compiler is misfiring here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-05 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 9:15 next-20160705 build: 2 failures 6 warnings (next-20160705) Build bot for Mark Brown
2016-07-05 9:52 ` Mark Brown [this message]
2016-07-05 10:00 ` [PATCH, RESEND] staging: emxx_udc: allow modular build Arnd Bergmann
2016-07-05 10:06 ` Felipe Balbi
2016-07-06 2:31 ` next-20160705 build: 2 failures 6 warnings (next-20160705) Peter Chen
2016-07-06 3:00 ` Peter Chen
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=20160705095242.GP6247@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=damm+renesas@opensource$(echo .)se \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=horms+renesas@verge$(echo .)net.au \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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