From: kbuild test robot <lkp@intel.com>
To: Tony Xie <tony.xie@rock-chips.com>
Cc: kbuild-all@01.org, Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH linux-next] mfd: rk808: rk8xx_pm_ops can be static
Date: Mon, 8 Jul 2019 15:08:43 +0800 [thread overview]
Message-ID: <20190708070843.GA23605@lkp-kbuild12> (raw)
In-Reply-To: <201907081550.e4JO1ctY%lkp@intel.com>
Fixes: 586c1b4125b3 ("mfd: rk808: Add RK817 and RK809 support")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
rk808.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c
index 6ee1c46..52666a9 100644
--- a/drivers/mfd/rk808.c
+++ b/drivers/mfd/rk808.c
@@ -751,7 +751,7 @@ static int rk8xx_resume(struct device *dev)
return ret;
}
-SIMPLE_DEV_PM_OPS(rk8xx_pm_ops, rk8xx_suspend, rk8xx_resume);
+static SIMPLE_DEV_PM_OPS(rk8xx_pm_ops, rk8xx_suspend, rk8xx_resume);
static struct i2c_driver rk808_i2c_driver = {
.driver = {
prev parent reply other threads:[~2019-07-08 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 7:08 [linux-next:master 9992/12641] drivers/mfd/rk808.c:754:1: sparse: sparse: symbol 'rk8xx_pm_ops' was not declared. Should it be static? kbuild test robot
2019-07-08 7:08 ` kbuild 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=20190708070843.GA23605@lkp-kbuild12 \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.xie@rock-chips.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
all inboxes | Powered by JetHome®