From: kernel test robot <lkp@intel.com>
To: Keith Busch <keith.busch@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Rajat Jain <rajatja@google.com>,
Gwendal Grignou <gwendal@chromium.org>
Subject: [RFC PATCH jsarha] BACKPORT: FROMGIT: nvme-pci: nvme_dev_pm_ops can be static
Date: Tue, 12 Apr 2022 03:24:45 +0800 [thread overview]
Message-ID: <YlSAffL1A6Q6BCZ0@efd45e54f7c9> (raw)
In-Reply-To: <202204120348.5EvqQlqc-lkp@intel.com>
drivers/nvme/host/pci.c:2705:25: warning: symbol 'nvme_dev_pm_ops' was not declared. Should it be static?
Fixes: bc7304877066 ("BACKPORT: FROMGIT: nvme-pci: Use host managed power state for suspend")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
drivers/nvme/host/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 23f999fef88bcb..a33a32e6787799 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -2702,7 +2702,7 @@ static int nvme_suspend(struct device *dev)
nvme_simple_suspend(dev) : nvme_deep_state(ndev);
}
-const struct dev_pm_ops nvme_dev_pm_ops = {
+static const struct dev_pm_ops nvme_dev_pm_ops = {
.suspend = nvme_suspend,
.resume = nvme_resume,
.freeze = nvme_simple_suspend,
prev parent reply other threads:[~2022-04-11 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 19:25 [jsarha:topic/chromeos-4.19-s0ix 7573/9999] drivers/nvme/host/pci.c:2705:25: sparse: sparse: symbol 'nvme_dev_pm_ops' was not declared. Should it be static? kernel test robot
2022-04-11 19:24 ` kernel test robot [this message]
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=YlSAffL1A6Q6BCZ0@efd45e54f7c9 \
--to=lkp@intel.com \
--cc=gwendal@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rajatja@google.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