From: Arnd Bergmann <arnd@arndb.de>
To: Build bot for Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: next-20170424 build: 1 failures 0 warnings (next-20170424)
Date: Tue, 25 Apr 2017 21:57:10 +0200 [thread overview]
Message-ID: <CAK8P3a2sFSojMioTmF06eSgQiAJNurhDLCzSAF6W0Qd4XOe=KA@mail.gmail.com> (raw)
In-Reply-To: <E1d2ca0-0002cs-HH@optimist>
On Mon, Apr 24, 2017 at 1:54 PM, Build bot for Mark Brown
<broonie@kernel.org> wrote:
> Tree/Branch: next-20170424
> Git describe: next-20170424
> Commit: ee91aaf669 Add linux-next specific files for 20170424
>
> Build Time: 116 min 41 sec
>
> Passed: 9 / 10 ( 90.00 %)
> Failed: 1 / 10 ( 10.00 %)
>
> Errors: 1
> Warnings: 0
> Section Mismatches: 0
>
> Failed defconfigs:
> arm-allmodconfig
>
> Errors:
>
> arm-allmodconfig
> ERROR: "__aeabi_uldivmod" [drivers/gpu/drm/arm/mali-dp.ko] undefined!
>
> -------------------------------------------------------------------------------
> defconfigs with issues (other than build errors):
>
> -------------------------------------------------------------------------------
>
> Errors summary: 1
> 1 ERROR: "__aeabi_uldivmod" [drivers/gpu/drm/arm/mali-dp.ko] undefined!
>
The regression just appeared with this release, I sent a patch now.
Arnd
prev parent reply other threads:[~2017-04-25 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 11:54 next-20170424 build: 1 failures 0 warnings (next-20170424) Build bot for Mark Brown
2017-04-25 19:57 ` Arnd Bergmann [this message]
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='CAK8P3a2sFSojMioTmF06eSgQiAJNurhDLCzSAF6W0Qd4XOe=KA@mail.gmail.com' \
--to=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-next@vger.kernel.org \
--cc=liviu.dudau@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).