[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1ca9f3e8e52ccbca151f00d0514fae9262791f55.camel@intel.com>
Date: Fri, 14 Oct 2022 17:01:42 +0800
From: Zhang Rui <rui.zhang@...el.com>
To: Peter Zijlstra <peterz@...radead.org>,
Dave Hansen <dave.hansen@...el.com>
Cc: 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 Fri, 2022-10-14 at 10:17 +0200, Peter Zijlstra wrote:
> 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 :-)
Thanks for pointing this out.
Patches updated with Fixes tag in V4 series.
thanks,
rui
Powered by blists - more mailing lists