From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH 5.15 000/927] 5.15.3-rc2 review
Date: Tue, 16 Nov 2021 20:12:33 -0800 [thread overview]
Message-ID: <20211117041233.GD212153@roeck-us.net> (raw)
In-Reply-To: <20211116142631.571909964@linuxfoundation.org>
On Tue, Nov 16, 2021 at 04:01:11PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.3 release.
> There are 927 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, 18 Nov 2021 14:24:22 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 154 pass: 153 fail: 1
Failed builds:
parisc:allmodconfig
Qemu test results:
total: 482 pass: 438 fail: 44
Failed tests:
<all arm64>
<all arm64be>
The parisc build failure as well as the arm64 crashes are all due
to the backported crypto patches, as already reported.
Guenter
prev parent reply other threads:[~2021-11-17 4:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 15:01 [PATCH 5.15 000/927] 5.15.3-rc2 review Greg Kroah-Hartman
2021-11-16 17:18 ` Naresh Kamboju
2021-11-16 19:00 ` Daniel Díaz
2021-11-17 7:59 ` Greg Kroah-Hartman
2021-11-16 18:18 ` Guenter Roeck
2021-11-17 7:59 ` Greg Kroah-Hartman
2021-11-16 18:43 ` Shuah Khan
2021-11-16 20:28 ` Florian Fainelli
2021-11-16 21:17 ` Fox Chen
2021-11-16 21:59 ` Scott Bruce
2021-11-17 5:41 ` Scott Bruce
2021-11-17 8:04 ` Greg Kroah-Hartman
2021-11-17 16:05 ` Scott Bruce
2021-11-18 17:09 ` Greg Kroah-Hartman
2021-11-17 4:12 ` Guenter Roeck [this message]
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=20211117041233.GD212153@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).