From: Benjamin Boortz <bennib@mailbox.org>
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@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 7.1 0000/2079] 7.1.5-rc2 review
Date: Thu, 23 Jul 2026 21:03:44 +0200 [thread overview]
Message-ID: <amJlVJqZPzYc8hWJ@bb-82jq> (raw)
In-Reply-To: <20260722142947.085426486@linuxfoundation.org>
On Wed, Jul 22, 2026 at 04:32:05PM +0200, Greg Kroah-Hartman wrote:
>This is the start of the stable review cycle for the 7.1.5 release.
>There are 2079 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, 24 Jul 2026 14:26:57 +0000.
>Anything received after that time might be too late.
Build and boot tested for x86_64, i386, arm64.
Tested-by: Benjamin Boortz <bennib@mailbox.org>
next prev parent reply other threads:[~2026-07-23 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 14:32 [PATCH 7.1 0000/2079] 7.1.5-rc2 review Greg Kroah-Hartman
2026-07-22 14:51 ` Ronald Warsow
2026-07-22 15:01 ` Brett A C Sheffield
2026-07-22 16:41 ` Jeffrin Thalakkottoor
2026-07-22 18:28 ` Pavel Machek
2026-07-22 19:05 ` Florian Fainelli
2026-07-22 21:56 ` Justin Forbes
2026-07-23 0:06 ` Barry K. Nathan
2026-07-23 18:34 ` Peter Schneider
2026-07-23 19:03 ` Benjamin Boortz [this message]
2026-07-25 1:24 ` Dileep malepu
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=amJlVJqZPzYc8hWJ@bb-82jq \
--to=bennib@mailbox.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@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@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--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