[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJvTdKkYTQzY1UsH_o2QdN1bS4gVfT87bEwMvgUXYwd+VFD+=w@mail.gmail.com>
Date: Thu, 13 Oct 2022 12:58:41 +0200
From: Len Brown <lenb@...nel.org>
To: Zhang Rui <rui.zhang@...el.com>
Cc: Dave Hansen <dave.hansen@...el.com>, 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, peterz@...radead.org, 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
This series of BUG FIXES needs to be marked for -stable.
What testing is it waiting for?
I don't see upstream, in linux-next or in tip -- which means that
nobody is testing it.
Are we supposed to be pulling from the URL below to get the latest???
The latest Intel Hybrid CPUs are sort of a mess without this series.
Distros will need to back-port it.
thanks,
-Len
On Fri, Sep 23, 2022 at 10:40 AM Zhang Rui <rui.zhang@...el.com> wrote:
>
> Hi, Dave,
>
> On Thu, 2022-09-22 at 09:53 -0700, Dave Hansen wrote:
> > > Changes since V2:
> > > - changelog improvements based on Peter' feedback
> > > - Remove combined tags
> >
> > I fixed those up and started testing your v2 yesterday.
>
> Thanks for doing this.
>
> > Can you
> > double-check that this:
> >
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git/log/?h=cpuid1f
> >
> > Looks the same as your v3?
>
> There is no code difference.
> Just that I have updated the subject and changelog of patch 1/8 per
> Peter' suggestion
> https://lore.kernel.org/lkml/8496afee057d63b83a7ff02ec7f1de8c2d0e97ae.camel@intel.com/
>
> thanks,
> rui
>
--
Len Brown, Intel
Powered by blists - more mailing lists