[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5c98c586-680c-29de-2bd8-f95a7fc7e432@intel.com>
Date: Sat, 18 Feb 2023 09:19:58 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Zhang, Rui" <rui.zhang@...el.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
Cc: "Brown, Len" <len.brown@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"zhang.jia@...ux.alibaba.com" <zhang.jia@...ux.alibaba.com>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [PATCH 1/1] x86/topology: fix erroneous smp_num_siblings on Intel
Hybrid platform
On 2/18/23 08:11, Zhang, Rui wrote:
> yes. I totally agree with this.
>
> But when showing the (cpu topology info and lscpu) problem below, I
> want to deliver a clear message that
> 1. there are two bugs and *both* of them are required in order to
> trigger the problem
> 2. this patch just fixes one of the bugs
That's fine, but please deliver that message in the cover letter, not
the patch changelog.
> Do you mean that I don't need to mention the x86_max_cores issue here?
Yes.
Powered by blists - more mailing lists