From: kernel test robot <lkp@intel.com>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>
Cc: llvm@lists.linux.dev, 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: [xilinx-xlnx:xlnx_rebase_v5.4 842/1768] drivers/spi/spi-mem.c:18:6: warning: no previous prototype for function 'update_stripe'
Date: Sat, 18 Dec 2021 08:37:47 +0800 [thread overview]
Message-ID: <202112180856.mN80AB8F-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v5.4
head: abafefebd1f1e040eef74e4ab571ea08bf745641
commit: 3780469dd372e934445de2fbb5e8cf6e712b9b99 [842/1768] spi: Add Zynq QSPI controller driver
config: x86_64-randconfig-r013-20211214 (https://download.01.org/0day-ci/archive/20211218/202112180856.mN80AB8F-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project b6a2ddb6c8ac29412b1361810972e15221fa021c)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/Xilinx/linux-xlnx/commit/3780469dd372e934445de2fbb5e8cf6e712b9b99
git remote add xilinx-xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xilinx-xlnx xlnx_rebase_v5.4
git checkout 3780469dd372e934445de2fbb5e8cf6e712b9b99
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/mtd/spi-nor/ drivers/spi/ drivers/usb/host/
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 >>):
>> drivers/spi/spi-mem.c:18:6: warning: no previous prototype for function 'update_stripe' [-Wmissing-prototypes]
bool update_stripe(const u8 opcode)
^
drivers/spi/spi-mem.c:18:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
bool update_stripe(const u8 opcode)
^
static
1 warning generated.
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-12-18 0:40 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=202112180856.mN80AB8F-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=llvm@lists.linux.dev \
--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 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).