From: kernel test robot <lkp@intel.com>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
Michal Simek <monstr@monstr.eu>,
Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
Harini Katakam <harinik@xilinx.com>,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
Soren Brinkmann <soren.brinkmann@xilinx.com>
Subject: [xlnx:xlnx_rebase_v5.4 842/1765] drivers/spi/spi-mem.c:18:6: sparse: sparse: symbol 'update_stripe' was not declared. Should it be static?
Date: Fri, 23 Jul 2021 00:06:53 +0800 [thread overview]
Message-ID: <202107230040.2NdfB545-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v5.4
head: 2f686fa6c0bf7fa168dc45dd7ce1359217212911
commit: 3780469dd372e934445de2fbb5e8cf6e712b9b99 [842/1765] spi: Add Zynq QSPI controller driver
config: i386-randconfig-s001-20210722 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/Xilinx/linux-xlnx/commit/3780469dd372e934445de2fbb5e8cf6e712b9b99
git remote add xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xlnx xlnx_rebase_v5.4
git checkout 3780469dd372e934445de2fbb5e8cf6e712b9b99
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/spi/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-mem.c:18:6: sparse: sparse: symbol 'update_stripe' was not declared. Should it be static?
vim +/update_stripe +18 drivers/spi/spi-mem.c
17
> 18 bool update_stripe(const u8 opcode)
19 {
20 if (opcode == SPINOR_OP_BE_4K ||
21 opcode == SPINOR_OP_BE_32K ||
22 opcode == SPINOR_OP_CHIP_ERASE ||
23 opcode == SPINOR_OP_SE ||
24 opcode == SPINOR_OP_BE_32K_4B ||
25 opcode == SPINOR_OP_SE_4B ||
26 opcode == SPINOR_OP_BE_4K_4B ||
27 opcode == SPINOR_OP_WRSR ||
28 opcode == SPINOR_OP_WREAR ||
29 opcode == SPINOR_OP_BRWR ||
30 opcode == SPINOR_OP_WRSR2)
31 return false;
32
33 return true;
34 }
35
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30582 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [xlnx:xlnx_rebase_v5.4 842/1765] drivers/spi/spi-mem.c:18:6: sparse: sparse: symbol 'update_stripe' was not declared. Should it be static?
Date: Fri, 23 Jul 2021 00:06:53 +0800 [thread overview]
Message-ID: <202107230040.2NdfB545-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v5.4
head: 2f686fa6c0bf7fa168dc45dd7ce1359217212911
commit: 3780469dd372e934445de2fbb5e8cf6e712b9b99 [842/1765] spi: Add Zynq QSPI controller driver
config: i386-randconfig-s001-20210722 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/Xilinx/linux-xlnx/commit/3780469dd372e934445de2fbb5e8cf6e712b9b99
git remote add xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xlnx xlnx_rebase_v5.4
git checkout 3780469dd372e934445de2fbb5e8cf6e712b9b99
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/spi/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-mem.c:18:6: sparse: sparse: symbol 'update_stripe' was not declared. Should it be static?
vim +/update_stripe +18 drivers/spi/spi-mem.c
17
> 18 bool update_stripe(const u8 opcode)
19 {
20 if (opcode == SPINOR_OP_BE_4K ||
21 opcode == SPINOR_OP_BE_32K ||
22 opcode == SPINOR_OP_CHIP_ERASE ||
23 opcode == SPINOR_OP_SE ||
24 opcode == SPINOR_OP_BE_32K_4B ||
25 opcode == SPINOR_OP_SE_4B ||
26 opcode == SPINOR_OP_BE_4K_4B ||
27 opcode == SPINOR_OP_WRSR ||
28 opcode == SPINOR_OP_WREAR ||
29 opcode == SPINOR_OP_BRWR ||
30 opcode == SPINOR_OP_WRSR2)
31 return false;
32
33 return true;
34 }
35
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30582 bytes --]
next reply other threads:[~2021-07-22 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 16:06 kernel test robot [this message]
2021-07-22 16:06 ` [xlnx:xlnx_rebase_v5.4 842/1765] drivers/spi/spi-mem.c:18:6: sparse: sparse: symbol 'update_stripe' was not declared. Should it be static? kernel test robot
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=202107230040.2NdfB545-lkp@intel.com \
--to=lkp@intel.com \
--cc=amit.kumar-mahapatra@xilinx.com \
--cc=harinik@xilinx.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=monstr@monstr.eu \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=punnaia@xilinx.com \
--cc=soren.brinkmann@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.