[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1703011151090.4005@nanos>
Date: Wed, 1 Mar 2017 11:52:22 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Dou Liyang <douly.fnst@...fujitsu.com>
cc: mingo@...nel.org, peterz@...radead.org, rjw@...ysocki.net,
hpa@...or.com, rafael@...nel.org, cl@...ux.com, tj@...nel.org,
akpm@...ux-foundation.org, rafael.j.wysocki@...el.com,
len.brown@...el.com, izumi.taku@...fujitsu.com,
xiaolong.ye@...el.com, x86@...nel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/4] Revert"x86/acpi: Enable MADT APIs to return
disabled apicids"
On Mon, 20 Feb 2017, Dou Liyang wrote:
> After we never do the last mapping of "cpuid <-> nodeid" at booting time. we
> also no need to enable MADT APIs to return disabled apicid.
>
> So, The patch work for reverting the commit 8ad893faf2:
> "x86/acpi: Enable MADT APIs to return disabled apicids"
Again, this changelog is confusing. A simple:
Remove the leftovers of the boot time 'cpuid <-> nodeid' mapping approach.
would be sufficient and entirely clear.
Thanks,
tglx
Powered by blists - more mailing lists