From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: Build bot for Mark Brown <broonie@kernel.org>,
kernel-build-reports@lists.linaro.org, stable@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: v4.4.12 build: 0 failures 3 warnings (v4.4.12)
Date: Thu, 02 Jun 2016 09:38:16 +0200 [thread overview]
Message-ID: <3699771.6rlE3xGWkm@wuerfel> (raw)
In-Reply-To: <E1b8Hwt-0001bT-9V@optimist>
On Thursday, June 2, 2016 3:01:27 AM CEST Build bot for Mark Brown wrote:
> -------------------------------------------------------------------------------
>
> Warnings Summary: 3
> 1 ../lib/lz4/lz4hc_compress.c:514:1: warning: the frame size of 1472 bytes is larger than 1024 bytes [-Wframe-larger-than=]
> 1 ../drivers/xen/balloon.c:155:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]
> 1 ../drivers/mtd/chips/cfi_cmdset_0020.c:651:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
That looks really nice! I hadn't noticed we were down that far with the
warnings.
The two stack warnings are fixed by c87bf431448b ("gcov: disable tree-loop-im
to reduce stack usage"), which is now in mainline. I think this warns about
a valid bug (gcc misoptimization leading to excessive stack usage).
Greg, would you consider that fix for backports?
The Xen warning unfortunately appeared with 58d378b24b7f ("xen/balloon: Fix
crash when ballooning on x86 32 bit PAE"), which was backported from mainline
into v4.4.10.
I made a fix that is in -next now, bdadcaf2a7c1 ("xen: remove incorrect
forward declaration"), but I don't know when that will get merged.
Arnd
next prev parent reply other threads:[~2016-06-02 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 2:01 v4.4.12 build: 0 failures 3 warnings (v4.4.12) Build bot for Mark Brown
2016-06-02 7:38 ` Arnd Bergmann [this message]
2016-06-02 15:27 ` Greg KH
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=3699771.6rlE3xGWkm@wuerfel \
--to=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@vger.kernel.org \
/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