From: Justin Forbes <jforbes@fedoraproject.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@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.15 000/192] 6.15.7-rc1 review
Date: Tue, 15 Jul 2025 14:54:33 -0600 [thread overview]
Message-ID: <aHbACXMz1Ype5uW5@fedora64.linuxtx.org> (raw)
In-Reply-To: <20250715130814.854109770@linuxfoundation.org>
On Tue, Jul 15, 2025 at 03:11:35PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.15.7 release.
> There are 192 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 Thu, 17 Jul 2025 13:07:32 +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.15.7-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.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Tested rc1 against the Fedora build system (aarch64, ppc64le, s390x,
x86_64), and boot tested x86_64. No regressions noted.
Tested-by: Justin M. Forbes <jforbes@fedoraproject.org>
next prev parent reply other threads:[~2025-07-15 20:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 13:11 [PATCH 6.15 000/192] 6.15.7-rc1 review Greg Kroah-Hartman
2025-07-15 13:12 ` [PATCH 6.15 025/192] arm64/mm: Drop wrong writes into TCR2_EL1 Greg Kroah-Hartman
2025-07-15 14:53 ` [PATCH 6.15 000/192] 6.15.7-rc1 review Ronald Warsow
2025-07-15 20:54 ` Justin Forbes [this message]
2025-07-15 21:11 ` Miguel Ojeda
2025-07-15 21:27 ` Takeshi Ogasawara
2025-07-15 21:34 ` Achill Gilgenast
2025-07-16 5:43 ` Luna Jernberg
2025-07-16 9:31 ` Naresh Kamboju
2025-07-16 10:16 ` Jon Hunter
2025-07-16 10:38 ` Mark Brown
2025-07-16 10:50 ` Ron Economos
2025-07-16 13:57 ` Pavel Machek
2025-07-16 14:13 ` Shuah Khan
2025-07-16 15:10 ` Markus Reichelt
2025-07-16 16:59 ` Peter Schneider
2025-07-16 17:27 ` Christian Heusel
2025-07-16 19:06 ` Florian Fainelli
2025-07-17 8:14 ` Brett A C Sheffield
-- strict thread matches above, loose matches on Subject: below --
2025-07-16 11:49 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=aHbACXMz1Ype5uW5@fedora64.linuxtx.org \
--to=jforbes@fedoraproject.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@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;
as well as URLs for NNTP newsgroup(s).