From: kernel test robot <lkp@intel.com>
To: "Amit, Kumar, Mahapatra," <amit.kumar-mahapatra@xilinx.com>
Cc: Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
Michal Simek <monstr@monstr.eu>,
kbuild-all@lists.01.org, Harini Katakam <harinik@xilinx.com>,
Soren Brinkmann <soren.brinkmann@xilinx.com>,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
linux-arm-kernel@lists.infradead.org
Subject: [xlnx:master 9537/10031] drivers/spi/spi-mem.c:18:6: sparse: sparse: symbol 'update_stripe' was not declared. Should it be
Date: Thu, 4 Jun 2020 06:27:47 +0800 [thread overview]
Message-ID: <202006040620.KNC6r6Nv%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
tree: https://github.com/Xilinx/linux-xlnx master
head: 3e983e4f0dfe5024dd0b4fedd5e46363f1dc9240
commit: 6cac93c63316f23909509a2894c5aba52d20a397 [9537/10031] spi: Add Zynq QSPI controller driver
config: i386-randconfig-s001-20200603 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-244-g0ee050a8-dirty
git checkout 6cac93c63316f23909509a2894c5aba52d20a397
# save the attached .config to linux build tree
make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
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?
Please review and possibly fold the followup patch.
---
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: 35195 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
next reply other threads:[~2020-06-03 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 22:27 kernel test robot [this message]
2020-06-03 22:27 ` [RFC PATCH xlnx] spi: update_stripe() can 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=202006040620.KNC6r6Nv%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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox