From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org,
kernel-build-reports@lists.linaro.org
Subject: Re: v3.10.105 build: 1 failures 174 warnings (v3.10.105)
Date: Mon, 27 Mar 2017 16:35:25 +0200 [thread overview]
Message-ID: <CAK8P3a0wda+t0pc062S+eoy_ipBzDRgdT85J6C1pfd30GeHRKw@mail.gmail.com> (raw)
In-Reply-To: <20170327143040.afe2toqvxhisk3m2@sirena.org.uk>
On Mon, Mar 27, 2017 at 4:30 PM, Mark Brown <broonie@kernel.org> wrote:
> On Mon, Mar 27, 2017 at 02:21:46PM +0200, Willy Tarreau wrote:
>> On Mon, Mar 27, 2017 at 12:27:41PM +0100, Build bot for Mark Brown wrote:
>
>> > arm64-allmodconfig
>> > /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
>
>> Interesting, nothing seems to have changed regrading this between
>> 3.10.104 and 3.10.105 so it's possible the issue is in fact older.
>> I do have an arm64 toolchain here, I'll try to figure what the problem
>> is.
>
> Yeah, my builds missed a few versions so it might not be new. It's
> possible this is a toolchain change, I think I upgraded while the builds
> weren't happening but ICBW.
The kernelci builder did not run into this problem on 3.10.105 or the
other kernels
(3.16, 3.12) that had the same issue on your builder. Kernelci uses
aarch64-linux-gcc-6.3.1. Which one do you have?
Arnd
next prev parent reply other threads:[~2017-03-27 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 11:27 v3.10.105 build: 1 failures 174 warnings (v3.10.105) Build bot for Mark Brown
2017-03-27 12:21 ` Willy Tarreau
2017-03-27 14:30 ` Mark Brown
2017-03-27 14:35 ` Arnd Bergmann [this message]
2017-03-27 14:40 ` Mark Brown
2017-03-28 7:28 ` Arnd Bergmann
2017-03-28 7:29 ` Arnd Bergmann
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=CAK8P3a0wda+t0pc062S+eoy_ipBzDRgdT85J6C1pfd30GeHRKw@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=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.