From: Arnd Bergmann <arnd@arndb.de>
To: kernel-build-reports@lists.linaro.org
Cc: Olof Johansson <olof@lixom.net>,
Olof's autobuilder <build@lixom.net>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mainline build: 896 warnings 1 failures (mainline/v4.6-rc5-224-gda9373d)
Date: Mon, 02 May 2016 09:24:19 +0200 [thread overview]
Message-ID: <1535117.FXDhxv6m8v@wuerfel> (raw)
In-Reply-To: <CAOesGMiwACS7Gq41c1p58h_Uj1RBz-_g-BQFZwgRTaKs6QwmvQ@mail.gmail.com>
On Sunday 01 May 2016 16:19:53 Olof Johansson wrote:
> On Sun, May 1, 2016 at 2:26 PM, Olof's autobuilder <build@lixom.net> wrote:
> > Here are the build results from automated periodic testing.
> >
> > The tree being built was mainline, found at:
> >
> > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git (master branch)
> >
> > Topmost commit:
> >
> > da9373d Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
> >
> > Build logs (stderr only) can be found at the following link (experimental):
> >
> > http://arm-soc.lixom.net/buildlogs/mainline/v4.6-rc5-224-gda9373d/
> >
> >
> > Runtime: 5m 0s
> >
> > Passed: 117
> > Failed: 1
> >
> > Warnings: 896
> >
> > Section mismatches: 0
>
> So, yeah, I updated to GCC 6.1.0 and it looks noisy. If it doesn't get
> whittled down pretty quickly I might switch to an older compiler
> again.
Oops, it looks like I never submitted a patch to shut up
-Wunused-const-variable, though I've been building that way
myself here and fixing all /other/ warnings.
I think we want to have -Wunused-const-variable at the W=1 level, but
not by default.
Arnd
next parent reply other threads:[~2016-05-02 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57267469.8ade420a.aec17.ffffc1ee@mx.google.com>
[not found] ` <CAOesGMiwACS7Gq41c1p58h_Uj1RBz-_g-BQFZwgRTaKs6QwmvQ@mail.gmail.com>
2016-05-02 7:24 ` Arnd Bergmann [this message]
2016-05-03 2:12 ` mainline build: 896 warnings 1 failures (mainline/v4.6-rc5-224-gda9373d) Olof Johansson
2016-05-03 20:16 ` 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=1535117.FXDhxv6m8v@wuerfel \
--to=arnd@arndb.de \
--cc=build@lixom.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kbuild@vger.kernel.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