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: [RFC PATCH spi] spi: lpspi: fsl_lpspi_runtime_resume() can be static
Date: Tue, 19 Mar 2019 09:46:33 +0800 [thread overview]
Message-ID: <20190319014633.GA8434@ivb42> (raw)
In-Reply-To: <201903190907.mIc3klXH%lkp@intel.com>
Fixes: 944c01a889d9 ("spi: lpspi: enable runtime pm for lpspi")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
spi-fsl-lpspi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-fsl-lpspi.c b/drivers/spi/spi-fsl-lpspi.c
index 1860f06..4de8eb3 100644
--- a/drivers/spi/spi-fsl-lpspi.c
+++ b/drivers/spi/spi-fsl-lpspi.c
@@ -780,7 +780,7 @@ static irqreturn_t fsl_lpspi_isr(int irq, void *dev_id)
return IRQ_NONE;
}
-int fsl_lpspi_runtime_resume(struct device *dev)
+static int fsl_lpspi_runtime_resume(struct device *dev)
{
struct fsl_lpspi_data *fsl_lpspi = dev_get_drvdata(dev);
int ret;
@@ -798,7 +798,7 @@ int fsl_lpspi_runtime_resume(struct device *dev)
return 0;
}
-int fsl_lpspi_runtime_suspend(struct device *dev)
+static int fsl_lpspi_runtime_suspend(struct device *dev)
{
struct fsl_lpspi_data *fsl_lpspi = dev_get_drvdata(dev);
next prev parent 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 [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? kbuild test robot
2019-03-19 1:46 ` kbuild test robot [this message]
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=20190319014633.GA8434@ivb42 \
--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).