From: kbuild test robot <lkp@intel.com>
To: Ludovic Barre <ludovic.barre@st.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
kbuild-all@01.org, Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [spi:for-5.2 8/8] drivers/spi/spi-stm32-qspi.c:520:1: sparse: symbol 'stm32_qspi_pm_ops' was not declared. Should it be static?
Date: Sat, 16 Mar 2019 15:33:40 +0800 [thread overview]
Message-ID: <201903161509.ZfXt4Lx6%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2
head: 2e541b64ee5269278fde5c87953a9963a8219ed4
commit: 2e541b64ee5269278fde5c87953a9963a8219ed4 [8/8] spi: spi-mem: stm32-qspi: add suspend/resume support
reproduce:
# apt-get install sparse
git checkout 2e541b64ee5269278fde5c87953a9963a8219ed4
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-stm32-qspi.c:520:1: sparse: symbol 'stm32_qspi_pm_ops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-03-16 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 7:33 kbuild test robot [this message]
2019-03-16 7:33 ` [RFC PATCH spi] spi: spi-mem: stm32-qspi: stm32_qspi_pm_ops can be static kbuild test robot
2019-03-20 17:30 ` Applied "spi: spi-mem: stm32-qspi: stm32_qspi_pm_ops can be static" to the spi tree Mark Brown
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=201903161509.ZfXt4Lx6%lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@st.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=ludovic.barre@st.com \
--cc=mcoquelin.stm32@gmail.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