From: kernel test robot <lkp@intel.com>
To: Hector Martin <marcan@marcan.st>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [asahilinux:wifi-wip 69/69] drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c:2024:1: warning: the frame size of 1032 bytes is larger than 1024 bytes
Date: Tue, 21 Dec 2021 15:09:36 +0800 [thread overview]
Message-ID: <202112211521.t1MoHFEv-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux wifi-wip
head: f23b880a0e670605f762a659fae44c4cb198bf8d
commit: f23b880a0e670605f762a659fae44c4cb198bf8d [69/69] WIP: wifi stuff
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20211221/202112211521.t1MoHFEv-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/AsahiLinux/linux/commit/f23b880a0e670605f762a659fae44c4cb198bf8d
git remote add asahilinux https://github.com/AsahiLinux/linux
git fetch --no-tags asahilinux wifi-wip
git checkout f23b880a0e670605f762a659fae44c4cb198bf8d
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/net/wireless/broadcom/brcm80211/brcmfmac/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c:32:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c: In function 'brcmf_pcie_parse_otp':
drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c:1960:18: warning: format '%ld' expects argument of type 'long int', but argument 4 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
1960 | brcmf_dbg(PCIE, "parse_otp size=%ld\n", size);
| ^~~~~~~~~~~~~~~~~~~~~~ ~~~~
| |
| size_t {aka unsigned int}
drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.h:77:7: note: in definition of macro 'brcmf_dbg'
77 | fmt, ##__VA_ARGS__); \
| ^~~
drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c:1960:36: note: format string is defined here
1960 | brcmf_dbg(PCIE, "parse_otp size=%ld\n", size);
| ~~^
| |
| long int
| %d
drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c: In function 'brcmf_pcie_read_otp':
>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c:2024:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
2024 | }
| ^
vim +2024 drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
1995
1996 static int brcmf_pcie_read_otp(struct brcmf_pciedev_info *devinfo)
1997 {
1998 u32 base, words, idx;
1999 u32 otp[BRCMF_OTP_MAX_WORDS];
2000 struct brcmf_core *core;
2001
2002 switch (devinfo->ci->chip) {
2003 case BRCM_CC_4387_CHIP_ID:
2004 base = 0x113c;
2005 words = 0x40;
2006 break;
2007 default:
2008 return 0;
2009 }
2010
2011 BUG_ON(words > BRCMF_OTP_MAX_WORDS);
2012
2013 core = brcmf_chip_get_core(devinfo->ci, BCMA_CORE_GCI);
2014 if (!core)
2015 return -ENODEV;
2016
2017 base += core->base;
2018
2019 for (idx = 0; idx < words; idx++) {
2020 otp[idx] = brcmf_pcie_buscore_read32(devinfo, base + 4 * idx);
2021 }
2022
2023 return brcmf_pcie_parse_otp(devinfo, (u8 *)otp, 4 * words);
> 2024 }
2025
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-21 7:09 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=202112211521.t1MoHFEv-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
/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®