From: Sven Joachim <svenjoac@gmx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net,
rwarsow@gmx.de, conor@kernel.org, hagar@microsoft.com,
broonie@kernel.org
Subject: Re: [PATCH 6.1 000/126] 6.1.116-rc1 review
Date: Thu, 07 Nov 2024 20:09:24 +0100 [thread overview]
Message-ID: <87pln63lp7.fsf@turtle.gmx.de> (raw)
In-Reply-To: <20241106120306.038154857@linuxfoundation.org> (Greg Kroah-Hartman's message of "Wed, 6 Nov 2024 13:03:21 +0100")
On 2024-11-06 13:03 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.116 release.
> There are 126 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 Fri, 08 Nov 2024 12:02:47 +0000.
> Anything received after that time might be too late.
Works fine for me on x86_64.
Tested-by: Sven Joachim <svenjoac@gmx.de>
Cheers,
Sven
next prev parent reply other threads:[~2024-11-07 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 12:03 [PATCH 6.1 000/126] 6.1.116-rc1 review Greg Kroah-Hartman
2024-11-06 16:53 ` SeongJae Park
2024-11-06 17:30 ` Pavel Machek
2024-11-07 2:40 ` Shuah Khan
2024-11-07 11:36 ` Peter Schneider
2024-11-07 11:50 ` Naresh Kamboju
2024-11-07 13:43 ` Jon Hunter
2024-11-07 19:09 ` Sven Joachim [this message]
2024-11-08 2:21 ` Ron Economos
2024-11-08 7:08 ` [PATCH 6.1] " Hardik Garg
2024-11-08 11:49 ` [PATCH 6.1 000/126] " Yann Sionneau
2024-11-08 15:45 ` Mark Brown
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=87pln63lp7.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hagar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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