The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.16 000/183] 6.16.6-rc1 review
Date: Mon, 8 Sep 2025 17:50:00 +0200	[thread overview]
Message-ID: <20250908155000.GH2771@pc21.mareichelt.com> (raw)
In-Reply-To: <20250907195615.802693401@linuxfoundation.org>

* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:

> This is the start of the stable review cycle for the 6.16.6 release.
> There are 183 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 Tue, 09 Sep 2025 19:55:53 +0000.
> Anything received after that time might be too late.

Hi Greg

6.16.6-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>

  parent reply	other threads:[~2025-09-08 15:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 19:57 [PATCH 6.16 000/183] 6.16.6-rc1 review Greg Kroah-Hartman
2025-09-08  1:49 ` Ronald Warsow
2025-09-08  3:41 ` Takeshi Ogasawara
2025-09-08  3:50 ` Florian Fainelli
2025-09-08  7:38 ` Achill Gilgenast
2025-09-08  9:25 ` Brett A C Sheffield
2025-09-08 11:31 ` Miguel Ojeda
2025-09-08 11:58 ` Peter Schneider
2025-09-08 15:02 ` Jon Hunter
2025-09-08 15:50 ` Markus Reichelt [this message]
2025-09-08 18:20 ` Justin Forbes
2025-09-08 22:35 ` Shuah Khan
2025-09-09  4:57 ` Dileep malepu
2025-09-09  5:47 ` Ron Economos
2025-09-09  8:14 ` Naresh Kamboju
2025-09-09 11:21 ` Mark Brown
2025-09-09 17:26 ` Christian Heusel
2025-09-09 17:48 ` 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=20250908155000.GH2771@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