[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y0ka/UKSEb36BPxt@hirez.programming.kicks-ass.net>
Date: Fri, 14 Oct 2022 10:17:01 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Zhang Rui <rui.zhang@...el.com>, Len Brown <lenb@...nel.org>,
linux-kernel@...r.kernel.org, x86@...nel.org,
linux-hwmon@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
corbet@....net, fenghua.yu@...el.com, jdelvare@...e.com,
linux@...ck-us.net, len.brown@...el.com
Subject: Re: [PATCH V3 0/8] x86/topology: Improve CPUID.1F handling
On Thu, Oct 13, 2022 at 08:19:03PM -0700, Dave Hansen wrote:
> On 10/13/22 19:06, Zhang Rui wrote:
> > Patch 4/8 ~ 5/8 are real fixes and they depends on patch 2/8 and 3/8 to
> > avoid possible regressions. So patch 2/8 ~ 5/8 should be stable
> > material.
> >
> > patch 6/8 is also a bugfix, but we have not observed any functionality
> > issues so far.
>
> If you want to make this really easy on me, you could take the changelog
> and comment revisions that I made in that testing branch that I shared,
> integrate them, and send it out again, and *only* include the bugfixes.
It's really simple; if it don't have a Fixes tag, it ain't a fix :-)
Powered by blists - more mailing lists