Re: [PATCH 5.19 000/362] 5.19.4-rc2 review

[Naresh Kamboju]

On Wed, 24 Aug 2022 at 12:31, Greg Kroah-Hartman
<gre...@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 5.19.4 release.
> There are 362 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 Fri, 26 Aug 2022 06:58:34 +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/v5.x/stable-review/patch-5.19.4-rc2.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Results from Linaro's test farm.
No regressions on arm64, arm, x86_64, and i386.

Tested-by: Linux Kernel Functional Testing <lk...@linaro.org>

NOTE:
x86_64 and arm64 clang nightly allmodconfig build failed.
sound/soc/atmel/mchp-spdiftx.c:508:20: error: implicit truncation from
'int' to bit-field changes value from 1 to -1
[-Werror,-Wbitfield-constant-conversion]
dev->gclk_enabled = 1;
^ ~
1 error generated.

clang-14-allmodconfig build pass on x86_64 and arm64.
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.19.y/build/v5.19.3-363-gafd9d04cfdb9/testrun/11542345/suite/build/test/clang-14-allmodconfig/history/

clang-nightly-allmodconfig build pass on x86_64 and arm64.
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.19.y/build/v5.19.3-363-gafd9d04cfdb9/testrun/11542345/suite/build/test/clang-nightly-allmodconfig/history/

## Build
* kernel: 5.19.4-rc2
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.19.y
* git commit: afd9d04cfdb9cff1b69e2ff10272ced56c641036
* git describe: v5.19.3-363-gafd9d04cfdb9
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.19.y/build/v5.19.3-363-gafd9d04cfdb9

## Test regressions (compared to v5.19.3)
* arm64, build
- clang-nightly-allmodconfig

* x86_64, build
- clang-nightly-allmodconfig
- https://builds.tuxbuild.com/2DntPWhfYK6ESM6Il3l6aIvKqes/

* riscv, build
- clang-nightly-allmodconfig
- clang-nightly-defconfig
- clang-nightly-tinyconfig
- https://builds.tuxbuild.com/2DntPYts34sHJI5VZuK5zKzkXr1/

## No metric Regressions (compared to v5.19.3)

## No test Fixes (compared to v5.19.3)

## No metric Fixes (compared to v5.19.3)

## Test result summary
total: 106629, pass: 95920, fail: 1031, skip: 9541, xfail: 137

## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 306 total, 303 passed, 3 failed
* arm64: 68 total, 65 passed, 3 failed
* i386: 57 total, 51 passed, 6 failed
* mips: 50 total, 47 passed, 3 failed
* parisc: 14 total, 14 passed, 0 failed
* powerpc: 65 total, 56 passed, 9 failed
* riscv: 32 total, 24 passed, 8 failed
* s390: 22 total, 20 passed, 2 failed
* sh: 26 total, 24 passed, 2 failed
* sparc: 14 total, 14 passed, 0 failed
* x86_64: 61 total, 58 passed, 3 failed

## Test suites summary
* fwts
* igt-gpu-tools
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-open-posix-tests
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* rcutorture
* v4l2-compliance
* vdso

--
Linaro LKFT
https://lkft.linaro.org

[Nathan Chancellor]

Hi Naresh,

This should be fixed in mainline soon:

https://git.kernel.org/broonie/sound/c/5c5c2baad2b55cc0a4b190266889959642298f79
https://github.com/ClangBuiltLinux/linux/issues/1686

It will conflict due to a lack of commit 403fcb5118a0 ("ASoC:
mchp-spdiftx: remove references to mchp_i2s_caps") in the stable trees
but I think that change can just be taken along with my change to
minimize any future conflicts. I'll send a separate email with that
information when my patch hits mainline.

Thanks as always for all the testing that you do!

Cheers,
Nathan