[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024020313-studio-pronto-db36@gregkh>
Date: Sat, 3 Feb 2024 07:40:06 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Daniel Díaz <daniel.diaz@...aro.org>
Cc: 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, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
conor@...nel.org, allen.lkml@...il.com,
mathias.nyman@...ux.intel.com, dmitry.baryshkov@...aro.org
Subject: Re: [PATCH 6.6 000/322] 6.6.16-rc1 review
On Sat, Feb 03, 2024 at 01:09:15AM -0600, Daniel Díaz wrote:
> Hello!
>
> On 02/02/24 10:01 p. m., Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.6.16 release.
> > There are 322 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Mon, 05 Feb 2024 03:51:47 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.16-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Same problems as reported on 6.7 and 6.1.
>
> Build error/warning ("variable 'slot_id' is uninitialized", as seen on 6.7 and 6.1) can be found on this branch too, with Clang 17 and Clang nightly on Arm64, Arm32, i386, x86, MIPS, RISC-V.
>
> Build error due to pmicintc is present on this branch too.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
Yeah, looks like the xhci changes here are not for stable as the fix it
makes is not correct here (it depends on other changes.) I'll go drop
them and push out new stable trees, hopefully that should resolve the
issues people are having.
thanks,
greg k-h
Powered by blists - more mailing lists