From: Palmer Dabbelt <palmer@dabbelt.com>
To: linux-riscv@lists.infradead.org
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
yash.shah@sifive.com, anup@brainfault.org, bp@suse.de,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel-team@android.com, kernel-team@android.com,
Palmer Dabbelt <palmerdabbelt@google.com>,
kbuild test robot <lkp@intel.com>
Subject: [PATCH 2/2] soc: sifive: l2 cache: Mark l2_get_priv_group as static
Date: Thu, 28 May 2020 15:43:53 -0700 [thread overview]
Message-ID: <20200528224353.32559-2-palmer@dabbelt.com> (raw)
In-Reply-To: <20200528224353.32559-1-palmer@dabbelt.com>
From: Palmer Dabbelt <palmerdabbelt@google.com>
The kbuild test robot is firing a warning over a missing prototype. The
function can just be static.
Reported-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
---
drivers/soc/sifive/sifive_l2_cache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/sifive/sifive_l2_cache.c b/drivers/soc/sifive/sifive_l2_cache.c
index 51e198880a8d..44d7e1951da3 100644
--- a/drivers/soc/sifive/sifive_l2_cache.c
+++ b/drivers/soc/sifive/sifive_l2_cache.c
@@ -133,7 +133,7 @@ static const struct attribute_group priv_attr_group = {
.attrs = priv_attrs,
};
-const struct attribute_group *l2_get_priv_group(struct cacheinfo *this_leaf)
+static const struct attribute_group *l2_get_priv_group(struct cacheinfo *this_leaf)
{
/* We want to use private group for L2 cache only */
if (this_leaf->level == 2)
--
2.27.0.rc0.183.gde8f92d652-goog
prev parent reply other threads:[~2020-05-28 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 22:43 [PATCH 1/2] soc: sifive: l2 cache: Eliminate an unsigned zero compare warning Palmer Dabbelt
2020-05-28 22:43 ` Palmer Dabbelt [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=20200528224353.32559-2-palmer@dabbelt.com \
--to=palmer@dabbelt.com \
--cc=anup@brainfault.org \
--cc=bp@suse.de \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=yash.shah@sifive.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).