From: "tip-bot2 for Alexander Shishkin" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/mm] x86/sev: Drop unneeded #include
Date: Wed, 11 Oct 2023 08:30:10 -0000 [thread overview]
Message-ID: <169701301076.3135.13127013166356652434.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20231010145220.3960055-3-alexander.shishkin@linux.intel.com>
The following commit has been merged into the x86/mm branch of tip:
Commit-ID: d6f274b7c8ac52abc81e898b62c3ff63fbeb11b8
Gitweb: https://git.kernel.org/tip/d6f274b7c8ac52abc81e898b62c3ff63fbeb11b8
Author: Alexander Shishkin <alexander.shishkin@linux.intel.com>
AuthorDate: Tue, 10 Oct 2023 17:52:20 +03:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Wed, 11 Oct 2023 10:15:47 +02:00
x86/sev: Drop unneeded #include
Commit:
20f07a044a76 ("x86/sev: Move common memory encryption code to mem_encrypt.c")
... forgot to remove the include of virtio_config.h from mem_encrypt_amd.c
when it moved the related code to mem_encrypt.c (from where this include
subsequently got removed by a later commit).
Remove it now.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Link: https://lore.kernel.org/r/20231010145220.3960055-3-alexander.shishkin@linux.intel.com
---
arch/x86/mm/mem_encrypt_amd.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/mm/mem_encrypt_amd.c b/arch/x86/mm/mem_encrypt_amd.c
index 62dde75..a68f2dd 100644
--- a/arch/x86/mm/mem_encrypt_amd.c
+++ b/arch/x86/mm/mem_encrypt_amd.c
@@ -19,7 +19,6 @@
#include <linux/kernel.h>
#include <linux/bitops.h>
#include <linux/dma-mapping.h>
-#include <linux/virtio_config.h>
#include <linux/cc_platform.h>
#include <asm/tlbflush.h>
next prev parent reply other threads:[~2023-10-11 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 14:52 [PATCH v3 0/2] x86/sev: Generalize sev_setup_arch() Alexander Shishkin
2023-10-10 14:52 ` [PATCH v3 1/2] x86/sev: Move sev_setup_arch() to mem_encrypt.c Alexander Shishkin
2023-10-11 8:30 ` [tip: x86/mm] " tip-bot2 for Alexander Shishkin
2023-10-10 14:52 ` [PATCH v3 2/2] x86/sev: Drop unneeded include Alexander Shishkin
2023-10-11 8:30 ` tip-bot2 for Alexander Shishkin [this message]
2023-10-10 20:46 ` [PATCH v3 0/2] x86/sev: Generalize sev_setup_arch() Tom Lendacky
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=169701301076.3135.13127013166356652434.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@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
all inboxes | Powered by JetHome®