linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [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?
@ 2019-03-16  7:33 kbuild test robot
  2019-03-16  7:33 ` [RFC PATCH spi] spi: spi-mem: stm32-qspi: stm32_qspi_pm_ops can be static kbuild test robot
  0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2019-03-16  7:33 UTC (permalink / raw)
  To: Ludovic Barre
  Cc: kbuild-all, linux-spi, Mark Brown, Maxime Coquelin,
	Alexandre Torgue, linux-stm32, linux-arm-kernel, linux-kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [RFC PATCH spi] spi: spi-mem: stm32-qspi: stm32_qspi_pm_ops can be static
  2019-03-16  7:33 [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? kbuild test robot
@ 2019-03-16  7:33 ` 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
  0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2019-03-16  7:33 UTC (permalink / raw)
  To: Ludovic Barre
  Cc: kbuild-all, linux-spi, Mark Brown, Maxime Coquelin,
	Alexandre Torgue, linux-stm32, linux-arm-kernel, linux-kernel


Fixes: 2e541b64ee52 ("spi: spi-mem: stm32-qspi: add suspend/resume support")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 spi-stm32-qspi.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/spi-stm32-qspi.c b/drivers/spi/spi-stm32-qspi.c
index 3e8ca10..7879a52 100644
--- a/drivers/spi/spi-stm32-qspi.c
+++ b/drivers/spi/spi-stm32-qspi.c
@@ -517,7 +517,7 @@ static int __maybe_unused stm32_qspi_resume(struct device *dev)
 	return 0;
 }
 
-SIMPLE_DEV_PM_OPS(stm32_qspi_pm_ops, stm32_qspi_suspend, stm32_qspi_resume);
+static SIMPLE_DEV_PM_OPS(stm32_qspi_pm_ops, stm32_qspi_suspend, stm32_qspi_resume);
 
 static const struct of_device_id stm32_qspi_match[] = {
 	{.compatible = "st,stm32f469-qspi"},

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Applied "spi: spi-mem: stm32-qspi: stm32_qspi_pm_ops can be static" to the spi tree
  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   ` Mark Brown
  0 siblings, 0 replies; 3+ messages in thread
From: Mark Brown @ 2019-03-20 17:30 UTC (permalink / raw)
  To: kbuild test robot
  Cc: Mark Brown, Ludovic Barre, kbuild-all, linux-spi, Mark Brown,
	Maxime Coquelin, Alexandre Torgue, linux-stm32, linux-arm-kernel,
	linux-kernel, linux-spi

The patch

   spi: spi-mem: stm32-qspi: stm32_qspi_pm_ops can be static

has been applied to the spi tree at

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git 

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.  

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

From 43a8d240eee4f523c7120f47a4c9469f5abfb308 Mon Sep 17 00:00:00 2001
From: kbuild test robot <lkp@intel.com>
Date: Sat, 16 Mar 2019 15:33:41 +0800
Subject: [PATCH] spi: spi-mem: stm32-qspi: stm32_qspi_pm_ops can be static

Fixes: 2e541b64ee52 ("spi: spi-mem: stm32-qspi: add suspend/resume support")
Signed-off-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
 drivers/spi/spi-stm32-qspi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/spi-stm32-qspi.c b/drivers/spi/spi-stm32-qspi.c
index 3e8ca10011cc..7879a523583c 100644
--- a/drivers/spi/spi-stm32-qspi.c
+++ b/drivers/spi/spi-stm32-qspi.c
@@ -517,7 +517,7 @@ static int __maybe_unused stm32_qspi_resume(struct device *dev)
 	return 0;
 }
 
-SIMPLE_DEV_PM_OPS(stm32_qspi_pm_ops, stm32_qspi_suspend, stm32_qspi_resume);
+static SIMPLE_DEV_PM_OPS(stm32_qspi_pm_ops, stm32_qspi_suspend, stm32_qspi_resume);
 
 static const struct of_device_id stm32_qspi_match[] = {
 	{.compatible = "st,stm32f469-qspi"},
-- 
2.20.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-03-20 17:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-16  7:33 [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? kbuild test robot
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

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).