From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Build bot for Mark Brown <broonie@kernel.org>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v3.18.52 build: 0 failures 2 warnings (v3.18.52)
Date: Mon, 8 May 2017 15:17:06 +0200 [thread overview]
Message-ID: <20170508131706.GA23246@kroah.com> (raw)
In-Reply-To: <CAK8P3a0P0MYO9bmEQ4-pXt_BMu-oyXq7QF5bEnAssdns9DgRqw@mail.gmail.com>
On Mon, May 08, 2017 at 02:25:11PM +0200, Arnd Bergmann wrote:
> On Mon, May 8, 2017 at 12:27 PM, Build bot for Mark Brown
> <broonie@kernel.org> wrote:
> > Tree/Branch: v3.18.52
> > Git describe: v3.18.52
> > Commit: 68e50dad01 Linux 3.18.52
>
> Ok, so while kernelci reports a clean build, both Olof and Mark still
> have one or two
> warnings.
>
> > defconfigs with issues (other than build errors):
> > 3 warnings 0 mismatches : arm-allmodconfig
> > 2 warnings 0 mismatches : arm-multi_v7_defconfig
> > 2 warnings 0 mismatches : arm-multi_v5_defconfig
>
> > Warnings Summary: 2
> > 6 ../drivers/tty/sysrq.c:956:33: warning: array subscript is above array bounds [-Warray-bounds]
>
> This was fixed in v4.2 with this patch:
>
> ffb6e0c9a057 ("tty: remove platform_sysrq_reset_seq")
>
> > 1 ../drivers/mtd/chips/cfi_cmdset_0020.c:651:1: warning: the frame size of 1192 bytes is larger than 1024 bytes [-Wframe-larger-than=]
>
> And this was fixed in v4.1 with
>
> d09957fbb4d0 ("mtd: cfi: reduce stack size")
>
> Both warnings are apparently architecture and gcc version specific, and kernelci
> had a different set of combinations here.
Both now queued up, thanks. Hopefully this should be the last ones for
these warnings :)
greg k-h
prev parent reply other threads:[~2017-05-08 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 10:27 v3.18.52 build: 0 failures 2 warnings (v3.18.52) Build bot for Mark Brown
2017-05-08 12:25 ` Arnd Bergmann
2017-05-08 13:17 ` gregkh [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=20170508131706.GA23246@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=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