From: Matthew Wilcox <willy@infradead.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-usb@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
lkft-triage@lists.linaro.org, Nick Terrell <terrelln@fb.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
cai.huoqing@linux.dev, Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [next] warning: the frame size of 1120 bytes is larger than 1024 bytes [-Wframe-larger-than=]
Date: Wed, 2 Mar 2022 14:19:07 +0000 [thread overview]
Message-ID: <Yh982ysEPvl5feRZ@casper.infradead.org> (raw)
In-Reply-To: <CA+G9fYvUHjwU9sOMs+zNwuauGLqah3Ce_5VKtifZucOuXqw2qA@mail.gmail.com>
On Wed, Mar 02, 2022 at 12:13:49PM +0530, Naresh Kamboju wrote:
> Following warnings noticed while building Linux next-20220301
> for arm KASAN builds [1].
Are any of them actually new? They all look pretty familiar to me,
and they don't have just one cause; they each need to be addressed
individually (if they need to be addressed at all).
prev parent reply other threads:[~2022-03-02 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 6:43 [next] warning: the frame size of 1120 bytes is larger than 1024 bytes [-Wframe-larger-than=] Naresh Kamboju
2022-03-02 14:19 ` Matthew Wilcox [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=Yh982ysEPvl5feRZ@casper.infradead.org \
--to=willy@infradead.org \
--cc=anders.roxell@linaro.org \
--cc=ast@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mathias.nyman@intel.com \
--cc=mchehab@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=terrelln@fb.com \
--cc=viro@zeniv.linux.org.uk \
/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).