From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH morse] x86/resctrl: domain_list_lock can be static
Date: Thu, 18 Nov 2021 08:25:01 +0800 [thread overview]
Message-ID: <20211118002501.GA74802@df6979b0ca98> (raw)
In-Reply-To: <202111180817.XpCUE0hP-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
arch/x86/kernel/cpu/resctrl/core.c:34:1: warning: symbol 'domain_list_lock' was not declared. Should it be static?
Fixes: 63dc771f7240 ("x86/resctrl: Split arch and fs resctrl locks")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/resctrl/core.c b/arch/x86/kernel/cpu/resctrl/core.c
index ae5d9e2d20b3b2..439078c4a676b3 100644
--- a/arch/x86/kernel/cpu/resctrl/core.c
+++ b/arch/x86/kernel/cpu/resctrl/core.c
@@ -31,7 +31,7 @@
* The rdt_resource's domain list is updated when this happens. The domain
* list is protected by cpuhp as a rwlock, writers also take this mutex.
*/
-DEFINE_MUTEX(domain_list_lock);
+static DEFINE_MUTEX(domain_list_lock);
/*
* The cached resctrl_pqr_state is strictly per CPU and can never be
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: James Morse <james.morse@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH morse] x86/resctrl: domain_list_lock can be static
Date: Thu, 18 Nov 2021 08:25:01 +0800 [thread overview]
Message-ID: <20211118002501.GA74802@df6979b0ca98> (raw)
In-Reply-To: <202111180817.XpCUE0hP-lkp@intel.com>
arch/x86/kernel/cpu/resctrl/core.c:34:1: warning: symbol 'domain_list_lock' was not declared. Should it be static?
Fixes: 63dc771f7240 ("x86/resctrl: Split arch and fs resctrl locks")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/resctrl/core.c b/arch/x86/kernel/cpu/resctrl/core.c
index ae5d9e2d20b3b2..439078c4a676b3 100644
--- a/arch/x86/kernel/cpu/resctrl/core.c
+++ b/arch/x86/kernel/cpu/resctrl/core.c
@@ -31,7 +31,7 @@
* The rdt_resource's domain list is updated when this happens. The domain
* list is protected by cpuhp as a rwlock, writers also take this mutex.
*/
-DEFINE_MUTEX(domain_list_lock);
+static DEFINE_MUTEX(domain_list_lock);
/*
* The cached resctrl_pqr_state is strictly per CPU and can never be
next prev parent reply other threads:[~2021-11-18 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 0:24 [morse:mpam/snapshot/v5.15 46/139] arch/x86/kernel/cpu/resctrl/core.c:34:1: sparse: sparse: symbol 'domain_list_lock' was not declared. Should it be static? kernel test robot
2021-11-18 0:24 ` kernel test robot
2021-11-18 0:25 ` kernel test robot [this message]
2021-11-18 0:25 ` [RFC PATCH morse] x86/resctrl: domain_list_lock can be static kernel test robot
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=20211118002501.GA74802@df6979b0ca98 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.