From: Borislav Petkov <bp@kernel.org>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: <linux-coco@lists.linux.dev>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: [PATCH 2/3] x86/sev: Add internal header guards
Date: Thu, 4 Dec 2025 13:48:07 +0100 [thread overview]
Message-ID: <20251204124809.31783-3-bp@kernel.org> (raw)
In-Reply-To: <20251204124809.31783-1-bp@kernel.org>
From: "Borislav Petkov (AMD)" <bp@alien8.de>
All headers need guards ifdeffery.
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
---
arch/x86/coco/sev/internal.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/coco/sev/internal.h b/arch/x86/coco/sev/internal.h
index c58c47c68ab6..af991f1da095 100644
--- a/arch/x86/coco/sev/internal.h
+++ b/arch/x86/coco/sev/internal.h
@@ -1,4 +1,6 @@
/* SPDX-License-Identifier: GPL-2.0 */
+#ifndef __X86_COCO_SEV_INTERNAL_H__
+#define __X86_COCO_SEV_INTERNAL_H__
#define DR7_RESET_VALUE 0x400
@@ -85,3 +87,4 @@ enum es_result sev_es_ghcb_handle_msr(struct ghcb *ghcb, struct es_em_ctxt *ctxt
u64 get_hv_features(void);
const struct snp_cpuid_table *snp_cpuid_get_table(void);
+#endif /* __X86_COCO_SEV_INTERNAL_H__ */
--
2.51.0
next prev parent reply other threads:[~2025-12-04 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 12:48 [PATCH 0/3] x86/sev: Carve out the SVSM support code Borislav Petkov
2025-12-04 12:48 ` [PATCH 1/3] x86/sev: Move the internal header Borislav Petkov
2025-12-04 14:18 ` Tom Lendacky
2025-12-04 14:57 ` Borislav Petkov
2025-12-04 12:48 ` Borislav Petkov [this message]
2025-12-04 12:48 ` [PATCH 3/3] x86/sev: Carve out the SVSM code into a separate compilation unit Borislav Petkov
2025-12-04 14:53 ` [PATCH 0/3] x86/sev: Carve out the SVSM support code Tom Lendacky
2025-12-04 15:06 ` 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=20251204124809.31783-3-bp@kernel.org \
--to=bp@kernel.org \
--cc=bp@alien8.de \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.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