From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: linux-next: build warnings after merge of the kbuild tree
Date: Thu, 31 May 2018 10:12:08 +0900 [thread overview]
Message-ID: <CAK7LNAQjVCPwfJ-opUkW3+XTM0uk9PSo3XiyGwCAMKkK05WnxA@mail.gmail.com> (raw)
In-Reply-To: <20180531084037.2f8b4c1e@canb.auug.org.au>
Hi.
(+CC Kees)
2018-05-31 7:40 GMT+09:00 Stephen Rothwell <sfr@canb.auug.org.au>:
> Hi Masahiro,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function 'wlc_phy_workarounds_nphy_rev7':
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:16563:1: warning: the frame size of 3136 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> }
> ^
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function 'wlc_phy_workarounds_nphy_rev3':
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:16905:1: warning: the frame size of 2872 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> }
> ^
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function 'wlc_phy_cal_txiqlo_nphy':
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:26033:1: warning: the frame size of 2432 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> }
> ^
>
> I have no idea what caused these warnings to appear ... nothing in those
> functions looks too bad.
This has been triggered by the following commit:
commit 0e461945f3504e09b8ecf947b6398adce1287a28
Author: Masahiro Yamada <yamada.masahiro@socionext.com>
Date: Mon May 28 18:22:07 2018 +0900
gcc-plugins: allow to enable GCC_PLUGINS for COMPILE_TEST
CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL was previously disabled
for COMPILE_TEST, which is now enabled.
COMPILE_TEST now enables GCC plugin for wider test coverage,
this is a good thing in general.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2018-05-31 1:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 22:40 linux-next: build warnings after merge of the kbuild tree Stephen Rothwell
2018-05-31 1:12 ` Masahiro Yamada [this message]
2018-05-31 1:26 ` Kees Cook
2018-05-31 3:53 ` Kees Cook
2018-06-01 1:56 ` Masahiro Yamada
2018-06-01 4:01 ` Kees Cook
2018-06-02 20:39 ` Arnd Bergmann
2018-06-04 8:39 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2022-06-01 23:28 Stephen Rothwell
2019-09-04 0:13 Stephen Rothwell
2019-09-04 1:00 ` Masahiro Yamada
2019-09-04 6:22 ` Masahiro Yamada
2019-09-04 12:33 ` Stephen Rothwell
2019-09-04 12:32 ` Stephen Rothwell
2017-07-19 0:05 Stephen Rothwell
2016-08-17 1:44 Stephen Rothwell
2016-08-17 12:59 ` Michal Marek
2016-08-18 1:09 ` Nicholas Piggin
2016-08-19 3:38 ` Stephen Rothwell
2016-08-19 5:09 ` Stephen Rothwell
2016-08-19 5:32 ` Nicholas Piggin
2016-08-19 8:37 ` Michal Marek
2016-08-19 10:44 ` Nicholas Piggin
2016-08-22 10:47 ` Nicholas Piggin
2016-08-26 3:58 ` Nicholas Piggin
2016-08-26 6:21 ` Nicholas Mc Guire
2016-06-09 2:22 Stephen Rothwell
2016-06-09 2:56 ` Kees Cook
2016-06-09 4:05 ` Stephen Rothwell
2016-06-09 10:57 ` Michal Marek
2016-06-09 17:37 ` Emese Revfy
2016-06-09 17:58 ` Kees Cook
2016-06-09 11:10 ` Michael Ellerman
2016-06-09 17:42 ` Emese Revfy
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=CAK7LNAQjVCPwfJ-opUkW3+XTM0uk9PSo3XiyGwCAMKkK05WnxA@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).