From: "tip-bot2 for Valdis Klētnieks" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: valdis.kletnieks@vt.edu, Borislav Petkov <bp@suse.de>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: x86/microcode] x86/microcode/AMD: Make stub function static inline
Date: Thu, 12 Dec 2019 21:33:55 -0000 [thread overview]
Message-ID: <157618643564.30329.7127565633998846101.tip-bot2@tip-bot2> (raw)
In-Reply-To: <52170.1575603873@turing-police>
The following commit has been merged into the x86/microcode branch of tip:
Commit-ID: 82c881b28aa89215a760e39c5f6bcde2d6ce4918
Gitweb: https://git.kernel.org/tip/82c881b28aa89215a760e39c5f6bcde2d6ce4918
Author: Valdis Klētnieks <valdis.kletnieks@vt.edu>
AuthorDate: Thu, 05 Dec 2019 22:44:33 -05:00
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Thu, 12 Dec 2019 22:29:00 +01:00
x86/microcode/AMD: Make stub function static inline
When building with C=1 W=1 (and when CONFIG_MICROCODE_AMD=n, as Luc Van
Oostenryck correctly points out) both sparse and gcc complain:
CHECK arch/x86/kernel/cpu/microcode/core.c
./arch/x86/include/asm/microcode_amd.h:56:6: warning: symbol \
'reload_ucode_amd' was not declared. Should it be static?
CC arch/x86/kernel/cpu/microcode/core.o
In file included from arch/x86/kernel/cpu/microcode/core.c:36:
./arch/x86/include/asm/microcode_amd.h:56:6: warning: no previous \
prototype for 'reload_ucode_amd' [-Wmissing-prototypes]
56 | void reload_ucode_amd(void) {}
| ^~~~~~~~~~~~~~~~
And they're right - that function can be a static inline like its
brethren.
Signed-off-by: Valdis Klētnieks <valdis.kletnieks@vt.edu>
Signed-off-by: Borislav Petkov <bp@suse.de>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: x86@kernel.org
Link: https://lkml.kernel.org/r/52170.1575603873@turing-police
---
arch/x86/include/asm/microcode_amd.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/microcode_amd.h b/arch/x86/include/asm/microcode_amd.h
index 2094928..6685e12 100644
--- a/arch/x86/include/asm/microcode_amd.h
+++ b/arch/x86/include/asm/microcode_amd.h
@@ -53,6 +53,6 @@ static inline void __init load_ucode_amd_bsp(unsigned int family) {}
static inline void load_ucode_amd_ap(unsigned int family) {}
static inline int __init
save_microcode_in_initrd_amd(unsigned int family) { return -EINVAL; }
-void reload_ucode_amd(void) {}
+static inline void reload_ucode_amd(void) {}
#endif
#endif /* _ASM_X86_MICROCODE_AMD_H */
prev parent reply other threads:[~2019-12-12 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 3:44 [PATCH] x86/microcode: make stub function static inline Valdis Klētnieks
2019-12-11 21:38 ` Borislav Petkov
2019-12-11 23:33 ` Valdis Klētnieks
2019-12-12 8:58 ` Borislav Petkov
2019-12-12 10:06 ` Luc Van Oostenryck
2019-12-12 10:49 ` Borislav Petkov
2019-12-12 12:22 ` David Laight
2019-12-12 21:33 ` tip-bot2 for Valdis Klētnieks [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=157618643564.30329.7127565633998846101.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=valdis.kletnieks@vt.edu \
--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).