From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.14 000/783] 6.14.9-rc1 review
Date: Wed, 28 May 2025 16:52:36 +0200 [thread overview]
Message-ID: <20250528145236.GA24108@pc21.mareichelt.com> (raw)
In-Reply-To: <20250527162513.035720581@linuxfoundation.org>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.14.9 release.
> There are 783 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, 29 May 2025 16:22:51 +0000.
> Anything received after that time might be too late.
Hi Greg
6.14.9-rc1 compiles, boots and runs here 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-05-28 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 16:16 Greg Kroah-Hartman
2025-05-27 16:20 ` [PATCH 6.14 207/783] arm64/mm: Check pmd_table() in pmd_trans_huge() Greg Kroah-Hartman
2025-05-27 16:20 ` [PATCH 6.14 208/783] arm64/mm: Check PUD_TYPE_TABLE in pud_bad() Greg Kroah-Hartman
2025-05-27 18:51 ` [PATCH 6.14 000/783] 6.14.9-rc1 review Florian Fainelli
2025-05-27 18:52 ` Ronald Warsow
2025-05-27 19:10 ` Naresh Kamboju
2025-05-28 8:50 ` Greg Kroah-Hartman
2025-05-27 22:14 ` Shuah Khan
2025-05-27 23:13 ` Peter Schneider
2025-05-27 23:24 ` Takeshi Ogasawara
2025-05-28 0:18 ` Miguel Ojeda
2025-05-28 6:50 ` Pavel Machek
2025-05-28 8:57 ` Ron Economos
2025-05-28 9:06 ` Christian Heusel
2025-05-28 11:26 ` Mark Brown
2025-05-28 14:52 ` Markus Reichelt [this message]
2025-05-28 19:00 ` Justin Forbes
2025-05-29 16:26 ` Hardik Garg
2025-06-04 9:40 ` 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=20250528145236.GA24108@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
all inboxes | Powered by JetHome®