[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wmy6u5tl.ffs@tglx>
Date: Mon, 07 Aug 2023 19:21:10 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
Tom Lendacky <thomas.lendacky@....com>,
Andrew Cooper <andrew.cooper3@...rix.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Huang Rui <ray.huang@....com>, Juergen Gross <jgross@...e.com>,
Dimitri Sivanich <dimitri.sivanich@....com>,
Michael Kelley <mikelley@...rosoft.com>,
Sohil Mehta <sohil.mehta@...el.com>,
K Prateek Nayak <kprateek.nayak@....com>,
Kan Liang <kan.liang@...ux.intel.com>,
Zhang Rui <rui.zhang@...el.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
Feng Tang <feng.tang@...el.com>,
Andy Shevchenko <andy@...radead.org>
Subject: Re: [patch 09/53] x86/mpparse: Rename default_find_smp_config()
On Mon, Aug 07 2023 at 19:03, Andy Shevchenko wrote:
> On Mon, Aug 7, 2023 at 4:52 PM Thomas Gleixner <tglx@...utronix.de> wrote:
>>
>> MPTABLE is not longer the default SMP configuration mechanism.
>
> not --> no
>
>> Rename it to mpparse_find_mptable() because that's what it does.
>
> ...
>
>> -#define enable_update_mptable 0
>
>> +#define enable_update_mptable (0)
>
> Hmm.. What's the point of this change?
Good question. Definitely not intentional.
Powered by blists - more mailing lists