From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.17 000/371] 6.17.4-rc1 review
Date: Sat, 18 Oct 2025 12:17:06 +0200 [thread overview]
Message-ID: <20251018101706.GA3227@pc21.mareichelt.com> (raw)
In-Reply-To: <20251017145201.780251198@linuxfoundation.org>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.17.4 release.
> There are 371 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 Sun, 19 Oct 2025 14:50:59 +0000.
> Anything received after that time might be too late.
Hi Greg
6.17.4-rc1 compiles on x86_64 (Xeon E5-1620 v2, Slackware64-15.0),
and boots & runs on x86_64 (AMD Ryzen 5 7520U, Slackware64-current).
No regressions observed.
Tested-by: Markus Reichelt <lkt+2023@mareichelt.com>
next prev parent reply other threads:[~2025-10-18 10:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 14:49 [PATCH 6.17 000/371] 6.17.4-rc1 review Greg Kroah-Hartman
2025-10-17 14:51 ` [PATCH 6.17 094/371] tools build: Align warning options with perf Greg Kroah-Hartman
2025-10-17 14:51 ` [PATCH 6.17 095/371] perf python: split Clang options when invoking Popen Greg Kroah-Hartman
2025-10-17 18:18 ` [PATCH 6.17 000/371] 6.17.4-rc1 review Ronald Warsow
2025-10-17 18:21 ` Jon Hunter
2025-10-17 21:47 ` Hardik Garg
2025-10-17 23:04 ` Ron Economos
2025-10-19 12:02 ` Greg Kroah-Hartman
2025-10-18 0:24 ` Shuah Khan
2025-10-18 3:45 ` Florian Fainelli
2025-10-18 3:53 ` Peter Schneider
2025-10-18 7:52 ` Brett A C Sheffield
2025-10-18 9:18 ` Dileep malepu
2025-10-18 10:17 ` Markus Reichelt [this message]
2025-10-18 16:19 ` Miguel Ojeda
2025-10-19 10:36 ` Pascal Ernster
2025-10-20 8:35 ` Naresh Kamboju
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=20251018101706.GA3227@pc21.mareichelt.com \
--to=lkt+2023@mareichelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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