From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.15 000/263] 6.15.5-rc2 review
Date: Sat, 5 Jul 2025 00:08:18 +0200 [thread overview]
Message-ID: <20250704220818.GB3473@pc21.mareichelt.com> (raw)
In-Reply-To: <20250704125604.759558342@linuxfoundation.org>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.15.5 release.
> There are 263 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.
Hi Greg
6.15.5-rc2 compiles on x86_64 (Xeon E5-1620 v2, Slackware64-15.0),
and boots on x86_64 (AMD Ryzen 5 7520U, Slackware64-current),
no dmesg regressions observed.
The difference in /sys/class/backlight/amdgpu_bl0/brightness value
compaired to kernel 6.15.4 and reported for -rc1 is still present.
Changing brightness with function keys in X works as before.
Not a problem, just a heads up for those of us who like to keep their
scripts simple.
Tested-by: Markus Reichelt <lkt+2023@mareichelt.com>
next prev parent reply other threads:[~2025-07-04 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 14:44 [PATCH 6.15 000/263] 6.15.5-rc2 review Greg Kroah-Hartman
2025-07-04 15:37 ` Ronald Warsow
2025-07-04 21:20 ` Mark Brown
2025-07-05 9:12 ` Luna Jernberg
2025-07-04 22:08 ` Markus Reichelt [this message]
2025-07-05 0:03 ` Miguel Ojeda
2025-07-05 0:04 ` Takeshi Ogasawara
2025-07-05 4:20 ` Peter Schneider
2025-07-05 20:46 ` Florian Fainelli
2025-07-05 22:03 ` Achill Gilgenast
2025-07-06 7:04 ` Pascal Ernster
2025-07-06 10:20 ` Naresh Kamboju
2025-07-07 18:34 ` Naresh Kamboju
2025-07-08 21:24 ` Naresh Kamboju
2025-07-09 8:19 ` Greg Kroah-Hartman
2025-07-07 8:43 ` 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=20250704220818.GB3473@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.