From: Markus Reichelt <lkt+2023@mareichelt.com>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1 000/200] 6.1.17-rc1 review
Date: Fri, 10 Mar 2023 17:42:18 +0100 [thread overview]
Message-ID: <20230310164218.GA2619@pc21.mareichelt.com> (raw)
In-Reply-To: <20230310133717.050159289@linuxfoundation.org>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.1.17 release.
> There are 200 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 Sun, 12 Mar 2023 13:36:38 +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/v6.x/stable-review/patch-6.1.17-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-6.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Hi Greg
6.1.17-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-03-10 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 13:36 [PATCH 6.1 000/200] 6.1.17-rc1 review Greg Kroah-Hartman
2023-03-10 13:38 ` [PATCH 6.1 116/200] kernel/printk/index.c: fix memory leak with using debugfs_lookup() Greg Kroah-Hartman
2023-03-10 16:42 ` Markus Reichelt [this message]
2023-03-10 18:58 ` [PATCH 6.1 000/200] 6.1.17-rc1 review Jon Hunter
2023-03-11 1:59 ` Shuah Khan
2023-03-11 3:39 ` Guenter Roeck
2023-03-11 4:13 ` Bagas Sanjaya
2023-03-11 5:58 ` Naresh Kamboju
2023-03-11 10:45 ` Conor Dooley
2023-03-11 12:29 ` Sudip Mukherjee
2023-03-11 18:02 ` Florian Fainelli
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=20230310164218.GA2619@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