From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
Build bot for Mark Brown <broonie@kernel.org>,
kernel-build-reports@lists.linaro.org,
linux-kernel@vger.kernel.org,
USB list <linux-usb@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: master build: 2 failures 3 warnings (v4.7-1605-ge658052)
Date: Tue, 26 Jul 2016 07:25:05 -0700 [thread overview]
Message-ID: <20160726142505.GB4460@kroah.com> (raw)
In-Reply-To: <3870219.tDBr8M1HNS@wuerfel>
On Tue, Jul 26, 2016 at 02:38:00PM +0200, Arnd Bergmann wrote:
> On Tuesday, July 26, 2016 1:29:55 PM CEST Build bot for Mark Brown wrote:
> > Tree/Branch: master
> > Git describe: v4.7-1605-ge658052
> > Commit: e65805251f Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> >
> > Build Time: 106 min 43 sec
> >
> > Passed: 7 / 9 ( 77.78 %)
> > Failed: 2 / 9 ( 22.22 %)
> >
> > Errors: 0
> > Warnings: 3
> > Section Mismatches: 0
> >
> > Failed defconfigs:
> > arm64-allmodconfig
> > arm-allmodconfig
>
> The build report doesn't actually show the error unfortunately, but
> I'm pretty sure it's this one:
>
> drivers/staging/built-in.o: In function `nbu2ss_drv_probe':
> (.text+0x2428): undefined reference to `usb_ep_set_maxpacket_limit'
>
> for which I sent a fix on June 22 and then again on July 5, with subject
> "staging: emxx_udc: allow modular build". Stephen Rothwell also reported
> that one yesterday.
>
> Greg, let me know if you'd like me to send that once more in case it's
> no longer in your queue.
Sorry, it's in my queue, let me get to it later today...
greg k-h
next prev parent reply other threads:[~2016-07-26 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1bS1Uh-0004bI-9C@optimist>
2016-07-26 12:38 ` Arnd Bergmann
2016-07-26 14:25 ` Greg KH [this message]
2016-07-26 14:39 ` Mark Brown
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=20160726142505.GB4460@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®