From: kbuild test robot <fengguang.wu@intel.com>
To: Andrew Banman <abanman@hpe.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Mike Travis <mike.travis@hpe.com>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <keescook@chromium.org>,
Colin Ian King <colin.king@canonical.com>,
Nicolai Stange <nstange@suse.de>
Subject: [RFC PATCH tip] x86/platform/uv/BAU: uv_bau_crash_shutdown() can be static
Date: Tue, 21 Aug 2018 02:14:16 +0800 [thread overview]
Message-ID: <20180820181416.GA85242@lkp-hsx02> (raw)
In-Reply-To: <201808210250.A3etcIJg%fengguang.wu@intel.com>
Fixes: 99f396587875 ("x86/platform/uv/BAU: Gracefully disable BAU during panic")
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
tlb_uv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/platform/uv/tlb_uv.c b/arch/x86/platform/uv/tlb_uv.c
index 4c1e119..bce4d14 100644
--- a/arch/x86/platform/uv/tlb_uv.c
+++ b/arch/x86/platform/uv/tlb_uv.c
@@ -2206,7 +2206,7 @@ static const struct bau_operations uv4_bau_ops __initconst = {
* Bring BAU to quiesence by abandoning current broadcasts and freeing up
* resources needed by firmware-initiated BAU broadcasts.
*/
-void uv_bau_crash_shutdown(struct pt_regs *regs)
+static void uv_bau_crash_shutdown(struct pt_regs *regs)
{
int pnode = 0;
int uvhub = 0;
next prev parent reply other threads:[~2018-08-20 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 18:14 [tip:x86/urgent 6/6] arch/x86/platform/uv/tlb_uv.c:2209:6: sparse: symbol 'uv_bau_crash_shutdown' was not declared. Should it be static? kbuild test robot
2018-08-20 18:14 ` kbuild test robot [this message]
2018-08-20 19:53 ` [RFC PATCH tip] x86/platform/uv/BAU: uv_bau_crash_shutdown() can be static Thomas Gleixner
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=20180820181416.GA85242@lkp-hsx02 \
--to=fengguang.wu@intel.com \
--cc=abanman@hpe.com \
--cc=colin.king@canonical.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@redhat.com \
--cc=nstange@suse.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.com \
--cc=x86@kernel.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 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).