From: kernel test robot <lkp@intel.com>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Michal Simek <monstr@monstr.eu>
Subject: [xilinx-xlnx:xlnx_rebase_v6.1 914/1065] drivers/spi/spi-zynq-qspi.c:167:6: warning: no previous prototype for 'zynq_qspi_update_stripe'
Date: Fri, 14 Apr 2023 03:58:18 +0800 [thread overview]
Message-ID: <202304140342.HGAB2WHR-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v6.1
head: bbf25ceb15a43c9047e14ab46a1d25c8ae6b67b4
commit: 2ac69c74ecee73f42f83efc33828cce52d831cfa [914/1065] spi: spi-zynq-qspi: Add multi-cs support in Zynq QSPI driver
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20230414/202304140342.HGAB2WHR-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.1.0
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/2ac69c74ecee73f42f83efc33828cce52d831cfa
git remote add xilinx-xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xilinx-xlnx xlnx_rebase_v6.1
git checkout 2ac69c74ecee73f42f83efc33828cce52d831cfa
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh SHELL=/bin/bash drivers/spi/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304140342.HGAB2WHR-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/spi/spi-zynq-qspi.c:167:6: warning: no previous prototype for 'zynq_qspi_update_stripe' [-Wmissing-prototypes]
167 | bool zynq_qspi_update_stripe(const struct spi_mem_op *op)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/zynq_qspi_update_stripe +167 drivers/spi/spi-zynq-qspi.c
159
160 /**
161 * zynq_qspi_update_stripe - For Zynq QSPI controller data stripe capabilities
162 * @op: Pointer to mem ops
163 * Return: Status of the data stripe
164 *
165 * Returns true if data stripe need to be enabled, else returns false
166 */
> 167 bool zynq_qspi_update_stripe(const struct spi_mem_op *op)
168 {
169 if (op->cmd.opcode == SPINOR_OP_BE_4K ||
170 op->cmd.opcode == SPINOR_OP_BE_32K ||
171 op->cmd.opcode == SPINOR_OP_CHIP_ERASE ||
172 op->cmd.opcode == SPINOR_OP_SE ||
173 op->cmd.opcode == SPINOR_OP_BE_32K_4B ||
174 op->cmd.opcode == SPINOR_OP_SE_4B ||
175 op->cmd.opcode == SPINOR_OP_BE_4K_4B ||
176 op->cmd.opcode == SPINOR_OP_WRSR ||
177 op->cmd.opcode == SPINOR_OP_WREAR ||
178 op->cmd.opcode == SPINOR_OP_BRWR ||
179 (op->cmd.opcode == SPINOR_OP_WRSR2 && !op->addr.nbytes))
180 return false;
181
182 return true;
183 }
184
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2023-04-13 20:00 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=202304140342.HGAB2WHR-lkp@intel.com \
--to=lkp@intel.com \
--cc=amit.kumar-mahapatra@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=monstr@monstr.eu \
--cc=oe-kbuild-all@lists.linux.dev \
/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).