From: Sohil Mehta <sohil.mehta@intel.com>
To: Wang Jinchao <wangjinchao@xfusion.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, <linux-kernel@vger.kernel.org>
Cc: <stone.xulei@xfusion.com>
Subject: Re: [PATCH] x86/setup: remove duplicated including
Date: Mon, 18 Dec 2023 17:27:46 +0530 [thread overview]
Message-ID: <16028dde-261a-4403-8165-f0a8b70f13fa@intel.com> (raw)
In-Reply-To: <202312151755+0800-wangjinchao@xfusion.com>
How about rewording the above to?
"x86/setup: Remove duplicate header includes"
On 12/15/2023 3:25 PM, Wang Jinchao wrote:
> rm the second #include <asm/efi.h> in setup.c
> rm the second #include <asm/spec-ctrl.h> in smpboot.c
Actually, these two lines are evident from the diff itself. You can
remove both of them. If you really want to have some text in the commit
message you can probably just say:
efi.h and spec-ctrl.h are included twice. Remove the duplicate entries.
>
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
> arch/x86/kernel/setup.c | 1 -
> arch/x86/kernel/smpboot.c | 1 -
> 2 files changed, 2 deletions(-)
>
With the above changes, please feel free to add:
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index 1526747bedf2..f6152c6b139a 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -37,7 +37,6 @@
> #include <asm/bugs.h>
> #include <asm/cacheinfo.h>
> #include <asm/cpu.h>
> -#include <asm/efi.h>
> #include <asm/gart.h>
> #include <asm/hypervisor.h>
> #include <asm/io_apic.h>
> diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
> index 2cc2aa120b4b..45057860e034 100644
> --- a/arch/x86/kernel/smpboot.c
> +++ b/arch/x86/kernel/smpboot.c
> @@ -87,7 +87,6 @@
> #include <asm/hw_irq.h>
> #include <asm/stackprotector.h>
> #include <asm/sev.h>
> -#include <asm/spec-ctrl.h>
>
> /* representing HT siblings of each logical CPU */
> DEFINE_PER_CPU_READ_MOSTLY(cpumask_var_t, cpu_sibling_map);
next prev parent reply other threads:[~2023-12-18 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 9:55 Wang Jinchao
2023-12-18 11:57 ` Sohil Mehta [this message]
2023-12-18 12:36 ` Wang Jinchao
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=16028dde-261a-4403-8165-f0a8b70f13fa@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stone.xulei@xfusion.com \
--cc=tglx@linutronix.de \
--cc=wangjinchao@xfusion.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®