From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
lkft-triage@lists.linaro.org, patches@kernelci.org,
patches@lists.linux.dev, pavel@denx.de, rwarsow@gmx.de,
shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH 6.15 000/589] 6.15.4-rc3 review
Date: Thu, 26 Jun 2025 19:39:32 +0200 [thread overview]
Message-ID: <20250626173932.1017297-1-ojeda@kernel.org> (raw)
In-Reply-To: <20250626105243.160967269@linuxfoundation.org>
On Thu, 26 Jun 2025 11:55:53 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.15.4 release.
> There are 589 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 Sat, 28 Jun 2025 10:51:38 +0000.
> Anything received after that time might be too late.
Boot-tested under QEMU for Rust x86_64, arm64 and riscv64; built-tested
for loongarch64:
Tested-by: Miguel Ojeda <ojeda@kernel.org>
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-06-26 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 10:55 [PATCH 6.15 000/589] 6.15.4-rc3 review Greg Kroah-Hartman
2025-06-26 11:45 ` Ronald Warsow
2025-06-26 14:38 ` Mark Brown
2025-06-26 17:33 ` Florian Fainelli
2025-06-26 17:39 ` Miguel Ojeda [this message]
2025-06-26 17:44 ` Naresh Kamboju
2025-06-26 22:33 ` Peter Schneider
2025-06-27 7:39 ` Jon Hunter
2025-06-27 8:14 ` Luna Jernberg
2025-06-27 9:39 ` Takeshi Ogasawara
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=20250626173932.1017297-1-ojeda@kernel.org \
--to=ojeda@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.