From: David Miller <davem@davemloft.net>
To: fengguang.wu@intel.com
Cc: nikolay@cumulusnetworks.com, kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [net-next:master 630/633] net/bridge/br_netlink.c:1110:1: warning: the frame size of 2160 bytes is larger than 2048 bytes
Date: Mon, 05 Oct 2015 02:47:17 -0700 (PDT) [thread overview]
Message-ID: <20151005.024717.1982719584385972843.davem@davemloft.net> (raw)
In-Reply-To: <201510051053.L0S9UKIW%fengguang.wu@intel.com>
From: kbuild test robot <fengguang.wu@intel.com>
Date: Mon, 5 Oct 2015 10:42:54 +0800
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> head: 3e087caa23ef36370bfb925d3bbca78e8302d3ce
> commit: 7e4df51eb35deedd3ba8d4db92a6c36fb7eff90a [630/633] bridge: netlink: add support for igmp's intervals
> config: x86_64-randconfig-s0-10051005 (attached as .config)
> reproduce:
> git checkout 7e4df51eb35deedd3ba8d4db92a6c36fb7eff90a
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All warnings (new ones prefixed by >>):
>
> net/bridge/br_netlink.c: In function 'br_fill_info':
>>> net/bridge/br_netlink.c:1110:1: warning: the frame size of 2160 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> }
Nikolay, please look into this.
next prev parent reply other threads:[~2015-10-05 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 2:42 [net-next:master 630/633] net/bridge/br_netlink.c:1110:1: warning: the frame size of 2160 bytes is larger than 2048 bytes kbuild test robot
2015-10-05 9:47 ` David Miller [this message]
2015-10-05 9:33 ` Nikolay Aleksandrov
2015-10-05 9:43 ` Nikolay Aleksandrov
2015-10-05 10:11 ` [PATCH net-next] bridge: netlink: make br_fill_info's frame size smaller Nikolay Aleksandrov
2015-10-07 11:16 ` David Miller
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=20151005.024717.1982719584385972843.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
/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).