[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b88ddaf-c5c5-0244-5be7-12400ee54e11@intel.com>
Date: Tue, 23 May 2023 10:52:48 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Saurabh Sengar <ssengar@...ux.microsoft.com>, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, kys@...rosoft.com,
haiyangz@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com,
mikelley@...rosoft.com, linux-kernel@...r.kernel.org,
linux-hyperv@...r.kernel.org
Cc: ssengar@...rosoft.com
Subject: Re: [PATCH 1/2] x86/Kconfig: Allow CONFIG_X86_MPPARSE disable for OF
platforms
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?
Powered by blists - more mailing lists