From: Richard Narron <richard@aaazen.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux stable <stable@vger.kernel.org>,
Linux kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 5.15 000/207] 5.15.185-rc1 review
Date: Mon, 2 Jun 2025 10:46:54 -0700 (PDT) [thread overview]
Message-ID: <2cb71dc9-a16b-5694-cb3-60a1815bdd84@aaazen.com> (raw)
In-Reply-To: <20250602134258.769974467@linuxfoundation.org>
On Mon, 2 Jun 2025, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.185 release.
> There are 207 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 Wed, 04 Jun 2025 13:42:20 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.185-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
The new kernel works fine on my miscellaneous Intel and AMD machines
running Slackware 15.0 both 32-bit and 64-bit.
Tested-by: Richard Narron <richard@aaazen.com>
next prev parent reply other threads:[~2025-06-02 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 13:46 [PATCH 5.15 000/207] 5.15.185-rc1 review Greg Kroah-Hartman
2025-06-02 13:47 ` [PATCH 5.15 054/207] arm64/mm: Check PUD_TYPE_TABLE in pud_bad() Greg Kroah-Hartman
2025-06-02 17:03 ` [PATCH 5.15 000/207] 5.15.185-rc1 review Florian Fainelli
2025-06-02 17:46 ` Richard Narron [this message]
2025-06-02 20:39 ` Pavel Machek
2025-06-03 4:02 ` Naresh Kamboju
2025-06-03 7:56 ` Greg Kroah-Hartman
2025-06-03 7:00 ` Ron Economos
2025-06-03 7:56 ` Greg Kroah-Hartman
2025-06-03 17:12 ` Shuah Khan
2025-06-03 17:24 ` Mark Brown
2025-06-03 20:22 ` 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=2cb71dc9-a16b-5694-cb3-60a1815bdd84@aaazen.com \
--to=richard@aaazen.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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