From: kbuild test robot <fengguang.wu@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: drivers/gpu//drm/tegra/sor.c:1245:1: warning: the frame size of 14656 bytes is larger than 8192 bytes
Date: Fri, 10 Nov 2017 01:49:02 +0800 [thread overview]
Message-ID: <201711100157.13eX9WjK%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 87df26175e67c26ccdd3a002fbbb8cde78e28a19
commit: 932f6529139ee7279e4c241eea46402ac7275936 drm/tegra: sor: Trace register accesses
date: 3 months ago
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 932f6529139ee7279e4c241eea46402ac7275936
# save the attached .config to linux build tree
make.cross ARCH=arm64
All warnings (new ones prefixed by >>):
drivers/gpu//drm/tegra/sor.c: In function 'tegra_sor_show_regs':
>> drivers/gpu//drm/tegra/sor.c:1245:1: warning: the frame size of 14656 bytes is larger than 8192 bytes [-Wframe-larger-than=]
}
^
vim +1245 drivers/gpu//drm/tegra/sor.c
dab16336 Thierry Reding 2015-01-26 1241
850bab44 Thierry Reding 2015-07-29 1242 unlock:
850bab44 Thierry Reding 2015-07-29 1243 drm_modeset_unlock_all(drm);
850bab44 Thierry Reding 2015-07-29 1244 return err;
dab16336 Thierry Reding 2015-01-26 @1245 }
dab16336 Thierry Reding 2015-01-26 1246
:::::: The code at line 1245 was first introduced by commit
:::::: dab163366a2a0f134cfa13a64ab750945648a18a drm/tegra: sor: Dump registers via debugfs
:::::: TO: Thierry Reding <treding@nvidia.com>
:::::: CC: Thierry Reding <treding@nvidia.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 56376 bytes --]
reply other threads:[~2017-11-09 17:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201711100157.13eX9WjK%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®