Re: [PATCH 6.1 000/198] 6.1.132-rc1 review

[Dragan Simic]

Hello Naresh,

On 2025-03-25 16:22, Naresh Kamboju wrote:
> On Tue, 25 Mar 2025 at 17:55, Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> > This is the start of the stable review cycle for the 6.1.132 release.
> > There are 198 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 Thu, 27 Mar 2025 12:21:27 +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.1.132-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.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Regressions on arm64 rk3399 dtb builds failed with gcc-13 the
> stable-rc 6.1.132-rc1
>
> First seen on the v6.1.131-199-gc8f0cb669e59
>  Good: v6.1.131
>  Bad: 6.1.132-rc1
>
> * arm64, build
>   - gcc-13-defconfig
>
> Regression Analysis:
>  - New regression? yes
>  - Reproducibility? Yes
>
> Build regression: arm64 dtb rockchip non-existent node or label 
> "vcca_0v9"
> Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx>
>
> ## Build log
> arch/arm64/boot/dts/rockchip/rk3399.dtsi:221.23-266.4: ERROR
> (phandle_references):
>   /pcie@f8000000: Reference to non-existent node or label "vcca_0v9"
>
>   also defined at 
> arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi:665.8-675.3
>
> ## Source
> * Kernel version: 6.1.132-rc1
> * Git tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> * Git sha: c8f0cb669e590c6c73c274b9fc56270ec33fa06b
> * Git describe: v6.1.131-199-gc8f0cb669e59
> * Project details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.131-199-gc8f0cb669e59/
>
> ## Build
> * Build log:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.131-199-gc8f0cb669e59/testrun/27755718/suite/build/test/gcc-13-lkftconfig-devicetree/log
> * Build history:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.131-199-gc8f0cb669e59/testrun/27755718/suite/build/test/gcc-13-lkftconfig-devicetree/history/
> * Build details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.131-199-gc8f0cb669e59/testrun/27755718/suite/build/test/gcc-13-lkftconfig-devicetree/details/
> * Build link:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2uoE2WrLPnhBvFm7ejgwd6QJxk8/
> * Kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2uoE2WrLPnhBvFm7ejgwd6QJxk8/config
>
> ## Steps to reproduce
>  - # tuxmake --runtime podman --target-arch arm64 --toolchain gcc-13
> --kconfig defconfig

This is caused by another patch from the original series failing
to apply due to some bulk regulator renaming.  I'll send backported
version of that patch soon, which should make everything fine.