[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024011935-snowman-regain-b820@gregkh>
Date: Fri, 19 Jan 2024 17:10:57 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Stefan Wiehler <stefan.wiehler@...ia.com>
Cc: Florian Fainelli <f.fainelli@...il.com>, stable@...r.kernel.org,
patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
conor@...nel.org, allen.lkml@...il.com
Subject: Re: [PATCH 6.1 000/100] 6.1.74-rc1 review
On Fri, Jan 19, 2024 at 05:07:08PM +0100, Stefan Wiehler wrote:
> Hi Florian,
>
> > It looks like rcutree_report_cpu_starting() has been introduced
> > 448e9f34d91d1a4799fdb06a93c2c24b34b6fd9d ("rcu: Standardize explicit
> > CPU-hotplug calls") which is in v6.7.
> >
> > For MIPS, it would like an adequate fix would be to
> > 's/rcutree_report_cpu_starting/rcu_cpu_starting/' for the 6.1 and 6.6
> > branches.
> >
> > Stefan, do you agree?
>
> Yes, I agree, that is also how the patch looks like in our internal branch
> based on 5.15.
Great, can someone send a working version of this patch for us to apply
for the next round of releases? It's dropped from all queues right now.
thanks,
greg k-h
Powered by blists - more mailing lists