From: kernel test robot <lkp@intel.com>
To: Joerg Roedel <jroedel@suse.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH joro] x86/sev: sev_jumptable_ap_park() can be static
Date: Thu, 8 Jul 2021 14:15:57 +0800 [thread overview]
Message-ID: <20210708061557.GA46859@4fc2f788f564> (raw)
In-Reply-To: <202107081415.O6XWbobR-lkp@intel.com>
arch/x86/kernel/sev.c:698:17: warning: symbol 'sev_jumptable_ap_park' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
sev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/sev.c b/arch/x86/kernel/sev.c
index bac9bb4fa54e0..3afddbd831b7a 100644
--- a/arch/x86/kernel/sev.c
+++ b/arch/x86/kernel/sev.c
@@ -695,7 +695,7 @@ static bool __init sev_es_setup_ghcb(void)
return true;
}
-void __noreturn sev_jumptable_ap_park(void)
+static void __noreturn sev_jumptable_ap_park(void)
{
local_irq_disable();
prev parent reply other threads:[~2021-07-08 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 6:15 [joro:sev-es-kexec 9/12] arch/x86/kernel/sev.c:698:17: sparse: sparse: symbol 'sev_jumptable_ap_park' was not declared. Should it be static? kernel test robot
2021-07-08 6:15 ` kernel 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=20210708061557.GA46859@4fc2f788f564 \
--to=lkp@intel.com \
--cc=jroedel@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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).