From: kbuild test robot <lkp@intel.com>
To: Han Xu <han.xu@nxp.com>
Cc: kbuild-all@01.org, linux-spi@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Clark Wang <xiaoning.wang@nxp.com>, Frank Li <frank.li@nxp.com>,
linux-kernel@vger.kernel.org
Subject: [spi:for-5.2 11/19] drivers/spi/spi-fsl-lpspi.c:483:5: sparse: symbol 'fsl_lpspi_runtime_resume' was not declared. Should it be static?
Date: Tue, 19 Mar 2019 09:46:33 +0800 [thread overview]
Message-ID: <201903190907.mIc3klXH%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2
head: 69b921acae8a5b7feef03921d9b42c3634f3b9d1
commit: 944c01a889d97dc08e1b71f4ed868f4023fd6034 [11/19] spi: lpspi: enable runtime pm for lpspi
reproduce:
# apt-get install sparse
git checkout 944c01a889d97dc08e1b71f4ed868f4023fd6034
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-fsl-lpspi.c:483:5: sparse: symbol 'fsl_lpspi_runtime_resume' was not declared. Should it be static?
>> drivers/spi/spi-fsl-lpspi.c:501:5: sparse: symbol 'fsl_lpspi_runtime_suspend' 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
next reply other threads:[~2019-03-19 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 1:46 kbuild test robot [this message]
2019-03-19 1:46 ` [RFC PATCH spi] spi: lpspi: fsl_lpspi_runtime_resume() can be static kbuild test robot
2019-03-19 13:14 ` Applied "spi: lpspi: fsl_lpspi_runtime_resume() 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=201903190907.mIc3klXH%lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=frank.li@nxp.com \
--cc=han.xu@nxp.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=xiaoning.wang@nxp.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).