From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
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,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org
Subject: Re: [PATCH 6.5 000/550] 6.5.12-rc1 review
Date: Thu, 16 Nov 2023 20:14:04 -0800 [thread overview]
Message-ID: <6c9f2a56-367a-455e-9d62-ebb507e225f0@roeck-us.net> (raw)
In-Reply-To: <20231115191600.708733204@linuxfoundation.org>
On Wed, Nov 15, 2023 at 02:09:44PM -0500, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.5.12 release.
> There are 550 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, 17 Nov 2023 19:14:03 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 157 pass: 155 fail: 2
Failed builds:
i386:allyesconfig
x86_64:allyesconfig
Qemu test results:
total: 530 pass: 100 fail: 430
Failed tests:
lots ...
I didn't check all failed tests, but it looks like the already reported
kunit build failures are responsible for at least a large majority of
the failures.
Guenter
prev parent reply other threads:[~2023-11-17 4:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 19:09 [PATCH 6.5 000/550] 6.5.12-rc1 review Greg Kroah-Hartman
2023-11-15 19:16 ` [PATCH 6.5 426/550] perf pmu: Remove logic for PMU name being NULL Greg Kroah-Hartman
2023-11-15 21:38 ` [PATCH 6.5 000/550] 6.5.12-rc1 review Daniel Díaz
2023-11-16 0:00 ` Daniel Díaz
2023-11-16 13:15 ` Naresh Kamboju
2023-11-16 14:02 ` Sasha Levin
2023-11-15 22:32 ` SeongJae Park
2023-11-16 20:05 ` Florian Fainelli
2023-11-16 22:43 ` Ron Economos
2023-11-17 4:14 ` 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=6c9f2a56-367a-455e-9d62-ebb507e225f0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.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=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;
as well as URLs for NNTP newsgroup(s).