From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.12 000/626] 6.12.31-rc1 review
Date: Wed, 28 May 2025 17:16:32 +0200 [thread overview]
Message-ID: <20250528151632.GB24108@pc21.mareichelt.com> (raw)
In-Reply-To: <20250527162445.028718347@linuxfoundation.org>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.12.31 release.
> There are 626 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.12.31-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-05-28 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 16:18 Greg Kroah-Hartman
2025-05-27 16:21 ` [PATCH 6.12 175/626] arm64/mm: Check pmd_table() in pmd_trans_huge() Greg Kroah-Hartman
2025-05-27 16:21 ` [PATCH 6.12 176/626] arm64/mm: Check PUD_TYPE_TABLE in pud_bad() Greg Kroah-Hartman
2025-05-27 18:43 ` [PATCH 6.12 000/626] 6.12.31-rc1 review Florian Fainelli
2025-05-27 22:15 ` Shuah Khan
2025-05-28 0:07 ` Peter Schneider
2025-05-28 0:18 ` Miguel Ojeda
2025-05-28 4:01 ` Harshit Mogalapalli
2025-05-28 6:36 ` Pavel Machek
2025-05-28 9:05 ` Ron Economos
2025-05-28 10:22 ` Naresh Kamboju
2025-05-28 10:51 ` Mark Brown
2025-05-28 13:01 ` Brett Mastbergen
2025-05-28 15:16 ` Markus Reichelt [this message]
2025-05-29 16:29 ` Hardik Garg
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=20250528151632.GB24108@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®