From: kbuild test robot <fengguang.wu@intel.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
Antoine Tenart <antoine.tenart@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Yan Markman <ymarkman@marvell.com>,
Stefan Chulski <stefanc@marvell.com>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH net-next] net: mvpp2: mvpp2_percpu_read_relaxed() can be static
Date: Sat, 2 Jun 2018 03:46:13 +0800 [thread overview]
Message-ID: <20180601194613.GA44770@xian> (raw)
In-Reply-To: <201806020329.B1k6qmEB%fengguang.wu@intel.com>
Fixes: db9d7d36eecc ("net: mvpp2: Split the PPv2 driver to a dedicated directory")
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
mvpp2_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c b/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
index 45622bf..0319ed9 100644
--- a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
+++ b/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
@@ -141,7 +141,7 @@ void mvpp2_percpu_write_relaxed(struct mvpp2 *priv, int cpu,
writel_relaxed(data, priv->swth_base[cpu] + offset);
}
-u32 mvpp2_percpu_read_relaxed(struct mvpp2 *priv, int cpu,
+static u32 mvpp2_percpu_read_relaxed(struct mvpp2 *priv, int cpu,
u32 offset)
{
return readl_relaxed(priv->swth_base[cpu] + offset);
next prev parent reply other threads:[~2018-06-01 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 19:46 [net-next:master 379/380] drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c:144:5: sparse: symbol 'mvpp2_percpu_read_relaxed' was not declared. Should it be static? kbuild test robot
2018-06-01 19:46 ` kbuild test robot [this message]
2018-06-04 15:36 ` [RFC PATCH net-next] net: mvpp2: mvpp2_percpu_read_relaxed() can be static David Miller
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=20180601194613.GA44770@xian \
--to=fengguang.wu@intel.com \
--cc=antoine.tenart@bootlin.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=ymarkman@marvell.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