From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 4.19 00/95] 4.19.322-rc2 review
Date: Fri, 13 Sep 2024 14:27:31 +0200 [thread overview]
Message-ID: <2024091329-clambake-lion-860a@gregkh> (raw)
In-Reply-To: <CA+G9fYtxOA7Ee1omhLT-fMaaBPqNEZQYVHXovLtGgv9jbuxQLA@mail.gmail.com>
On Wed, Sep 11, 2024 at 08:44:13PM +0530, Naresh Kamboju wrote:
> On Tue, 10 Sept 2024 at 16:18, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 4.19.322 release.
> > There are 95 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, 12 Sep 2024 09:42:36 +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/v4.x/stable-review/patch-4.19.322-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-4.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 <lkft@linaro.org>
>
> ## Build
> * kernel: 4.19.322-rc2
> * git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> * git commit: 00a71bfa9b89c96b41773efee1cca378cc1fa5e6
> * git describe: v4.19.321-96-g00a71bfa9b89
> * test details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19.321-96-g00a71bfa9b89
>
> ## Test Regressions (compared to v4.19.320-99-g0cc44dd838a6)
>
> ## Metric Regressions (compared to v4.19.320-99-g0cc44dd838a6)
>
> ## Test Fixes (compared to v4.19.320-99-g0cc44dd838a6)
>
> ## Metric Fixes (compared to v4.19.320-99-g0cc44dd838a6)
>
> ## Test result summary
> total: 116497, pass: 103587, fail: 542, skip: 12283, xfail: 85
>
> ## Build Summary
> * arc: 20 total, 20 passed, 0 failed
> * arm: 204 total, 192 passed, 12 failed
> * arm64: 54 total, 44 passed, 10 failed
> * i386: 30 total, 24 passed, 6 failed
> * mips: 40 total, 40 passed, 0 failed
> * parisc: 6 total, 0 passed, 6 failed
> * powerpc: 48 total, 48 passed, 0 failed
> * s390: 12 total, 12 passed, 0 failed
> * sh: 20 total, 20 passed, 0 failed
> * sparc: 12 total, 12 passed, 0 failed
> * x86_64: 46 total, 36 passed, 10 failed
>
> ## Test suites summary
> * boot
> * kunit
> * libhugetlbfs
> * log-parser-boot
> * log-parser-test
> * ltp-commands
> * ltp-containers
> * ltp-controllers
> * ltp-cpuhotplug
> * ltp-crypto
> * ltp-cve
> * ltp-dio
> * ltp-fcntl-locktests
> * ltp-fs
> * ltp-fs_bind
> * ltp-fs_perms_simple
> * ltp-hugetlb
> * ltp-ipc
> * ltp-math
> * ltp-mm
> * ltp-nptl
> * ltp-pty
> * ltp-sched
> * ltp-smoke
> * ltp-syscalls
> * ltp-tracing
> * rcutorture
>
> --
> Linaro LKFT
> https://lkft.linaro.org
>
Thanks for testing and letting me know,
greg k-h
next prev parent reply other threads:[~2024-09-13 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 9:43 [PATCH 4.19 00/95] 4.19.322-rc2 review Greg Kroah-Hartman
2024-09-10 18:44 ` Harshit Mogalapalli
2024-09-11 15:14 ` Naresh Kamboju
2024-09-13 12:27 ` Greg Kroah-Hartman [this message]
2024-09-11 17:28 ` Shuah Khan
2024-09-11 19:59 ` Pavel Machek
2024-09-12 7:17 ` Jon Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024091329-clambake-lion-860a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox