From: Dave Hansen <dave.hansen@intel.com>
To: Saurabh Sengar <ssengar@linux.microsoft.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, mikelley@microsoft.com,
linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org
Cc: ssengar@microsoft.com
Subject: Re: [PATCH 1/2] x86/Kconfig: Allow CONFIG_X86_MPPARSE disable for OF platforms
Date: Tue, 23 May 2023 10:52:48 -0700 [thread overview]
Message-ID: <9b88ddaf-c5c5-0244-5be7-12400ee54e11@intel.com> (raw)
In-Reply-To: <1683816877-10747-1-git-send-email-ssengar@linux.microsoft.com>
On 5/11/23 07:54, Saurabh Sengar wrote:
> X86_MPPARSE is only selectable when ACPI is enabled. However,
> on Devicetree platforms where ACPI is disabled, it is always
> enabled. Allow X86_MPPARSE to be selected by OF platforms as
> well.
I'm finding this changelog really hard to read.
In Kconfig, you can "select FOO". But in this changelog, it means
something different. I think "selectable" here means that there's a
user prompt for the option.
Could you please rephrase this to be less confusing?
This is also one of those patches where I wonder: Why do _you_ care
about this? Are you just trying to be nice? Is this intended as some
kind of cleanup?
next prev parent reply other threads:[~2023-05-23 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 14:54 Saurabh Sengar
2023-05-11 14:54 ` [PATCH 2/2] Drivers: hv: Kconfig: Add HYPERV_VTL_MODE dependencies Saurabh Sengar
2023-05-20 16:50 ` Michael Kelley (LINUX)
2023-05-24 16:09 ` Saurabh Singh Sengar
2023-05-20 16:39 ` [PATCH 1/2] x86/Kconfig: Allow CONFIG_X86_MPPARSE disable for OF platforms Michael Kelley (LINUX)
2023-05-23 17:52 ` Dave Hansen [this message]
2023-05-24 16:23 ` [EXTERNAL] " Saurabh Singh Sengar
2023-05-24 18:02 ` Dave Hansen
2023-05-25 7:06 ` Saurabh Singh Sengar
2023-05-25 13:56 ` Dave Hansen
2023-06-02 12:22 ` Saurabh Singh Sengar
2023-06-02 14:23 ` Dave Hansen
2023-06-02 16:25 ` [EXTERNAL] " Saurabh Singh Sengar
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=9b88ddaf-c5c5-0244-5be7-12400ee54e11@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@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
all inboxes | Powered by JetHome®