From: "Huang, Kai" <kai.huang@intel.com>
To: "jiapeng.chong@linux.alibaba.com"
<jiapeng.chong@linux.alibaba.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"bp@alien8.de" <bp@alien8.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"abaci@linux.alibaba.com" <abaci@linux.alibaba.com>
Subject: Re: [PATCH] x86/virt/tdx: Remove duplicate include
Date: Fri, 22 Mar 2024 06:38:35 +0000 [thread overview]
Message-ID: <363e70a764b252250dd5f2b91c68c0818b3068f3.camel@intel.com> (raw)
In-Reply-To: <20240322061741.9869-1-jiapeng.chong@linux.alibaba.com>
On Fri, 2024-03-22 at 14:17 +0800, Jiapeng Chong wrote:
> ./arch/x86/virt/vmx/tdx/tdx.c: linux/acpi.h is included more than once.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=8609
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> arch/x86/virt/vmx/tdx/tdx.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/virt/vmx/tdx/tdx.c b/arch/x86/virt/vmx/tdx/tdx.c
> index 4d6826a76f78..49a1c6890b55 100644
> --- a/arch/x86/virt/vmx/tdx/tdx.c
> +++ b/arch/x86/virt/vmx/tdx/tdx.c
> @@ -27,7 +27,6 @@
> #include <linux/log2.h>
> #include <linux/acpi.h>
> #include <linux/suspend.h>
> -#include <linux/acpi.h>
> #include <asm/page.h>
> #include <asm/special_insns.h>
> #include <asm/msr-index.h>
Thanks:
Reviewed-by: Kai Huang <kai.huang@intel.com>
prev parent reply other threads:[~2024-03-22 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 6:17 [PATCH] x86/virt/tdx: Remove duplicate include Jiapeng Chong
2024-03-22 6:38 ` Huang, Kai [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=363e70a764b252250dd5f2b91c68c0818b3068f3.camel@intel.com \
--to=kai.huang@intel.com \
--cc=abaci@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).