From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.2 000/242] 6.2.16-rc1 review
Date: Tue, 16 May 2023 20:23:44 +0200 [thread overview]
Message-ID: <20230516182344.GB29533@pc21.mareichelt.com> (raw)
In-Reply-To: <20230515161721.802179972@linuxfoundation.org>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.2.16 release.
> There are 242 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, 17 May 2023 16:16:37 +0000.
> Anything received after that time might be too late.
Hi Greg
6.2.16-rc1
compiles, boots and runs here on x86_64
(AMD Ryzen 5 PRO 4650G, Slackware64-15.0)
Tested-by: Markus Reichelt <lkt+2023@mareichelt.com>
next prev parent reply other threads:[~2023-05-16 18:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 16:25 [PATCH 6.2 000/242] 6.2.16-rc1 review Greg Kroah-Hartman
2023-05-15 16:26 ` [PATCH 6.2 059/242] rxrpc: Fix hard call timeout units Greg Kroah-Hartman
2023-05-15 16:26 ` [PATCH 6.2 060/242] rxrpc: Make it so that a waiting process can be aborted Greg Kroah-Hartman
2023-05-15 16:26 ` [PATCH 6.2 061/242] rxrpc: Fix timeout of a call that hasnt yet been granted a channel Greg Kroah-Hartman
2023-05-15 20:12 ` [PATCH 6.2 000/242] 6.2.16-rc1 review Chris Paterson
2023-05-16 1:22 ` Shuah Khan
2023-05-16 5:12 ` Ron Economos
2023-05-16 8:54 ` Bagas Sanjaya
2023-05-16 9:19 ` Sudip Mukherjee (Codethink)
2023-05-16 12:04 ` Naresh Kamboju
2023-05-16 12:06 ` Justin Forbes
2023-05-16 12:26 ` Conor Dooley
2023-05-16 18:23 ` Markus Reichelt [this message]
2023-05-17 2:53 ` Guenter Roeck
2023-05-17 7:55 ` 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=20230516182344.GB29533@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