From: Benjamin Thiel <b.thiel@posteo.de>
To: Borislav Petkov <bp@alien8.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>
Cc: x86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Benjamin Thiel <b.thiel@posteo.de>
Subject: [PATCH] x86/xen: Fix a -Wmissing prototypes warning for xen_start_kernel()
Date: Sat, 6 Jun 2020 16:27:21 +0200 [thread overview]
Message-ID: <20200606142721.19486-1-b.thiel@posteo.de> (raw)
Fix:
arch/x86/xen/enlighten_pv.c:1212:34:
warning: no previous prototype for ‘xen_start_kernel’ [-Wmissing-prototypes]
asmlinkage __visible void __init xen_start_kernel(void)
Add a prototype for xen_start_kernel() in a separate xen-specific header.
Signed-off-by: Benjamin Thiel <b.thiel@posteo.de>
---
arch/x86/include/asm/xen/setup.h | 7 +++++++
arch/x86/xen/enlighten_pv.c | 1 +
2 files changed, 8 insertions(+)
create mode 100644 arch/x86/include/asm/xen/setup.h
diff --git a/arch/x86/include/asm/xen/setup.h b/arch/x86/include/asm/xen/setup.h
new file mode 100644
index 000000000000..b7bd97f4b837
--- /dev/null
+++ b/arch/x86/include/asm/xen/setup.h
@@ -0,0 +1,7 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+#ifndef _ASM_X86_XEN_SETUP_H
+#define _ASM_X86_XEN_SETUP_H
+
+asmlinkage __visible void __init xen_start_kernel(void);
+
+#endif /*_ASM_X86_XEN_SETUP_H */
diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
index 35321f4d49f1..dc0850f09c70 100644
--- a/arch/x86/xen/enlighten_pv.c
+++ b/arch/x86/xen/enlighten_pv.c
@@ -55,6 +55,7 @@
#include <asm/xen/hypercall.h>
#include <asm/xen/hypervisor.h>
#include <asm/xen/cpuid.h>
+#include <asm/xen/setup.h>
#include <asm/fixmap.h>
#include <asm/processor.h>
#include <asm/proto.h>
--
2.20.1
next reply other threads:[~2020-06-06 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 14:27 Benjamin Thiel [this message]
2020-06-08 19:30 ` [PATCH] x86/xen: Fix a -Wmissing prototypes warning for xen_start_kernel() Boris Ostrovsky
2020-06-08 19:42 ` Borislav Petkov
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=20200606142721.19486-1-b.thiel@posteo.de \
--to=b.thiel@posteo.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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).