From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: achill@achill.org, 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@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH 6.19 000/311] 6.19.12-rc2 review
Date: Thu, 9 Apr 2026 17:58:21 +0200 [thread overview]
Message-ID: <20260409155821.35076-1-ojeda@kernel.org> (raw)
In-Reply-To: <20260409091742.514769762@linuxfoundation.org>
On Thu, 09 Apr 2026 11:25:28 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.19.12 release.
> There are 311 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, 11 Apr 2026 09:16:46 +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>
(arm 32-bit seems to build-test fine as well. Same for UML x86_64 on
a non-debug configuration.)
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2026-04-09 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 9:25 [PATCH 6.19 000/311] 6.19.12-rc2 review Greg Kroah-Hartman
2026-04-09 10:54 ` Ronald Warsow
2026-04-09 11:31 ` Luna Jernberg
2026-04-09 12:47 ` Takeshi Ogasawara
2026-04-09 13:22 ` Mark Brown
2026-04-09 15:58 ` Miguel Ojeda [this message]
2026-04-09 17:15 ` Jon Hunter
2026-04-09 17:55 ` Justin Forbes
2026-04-09 18:23 ` Peter Schneider
2026-04-09 18:41 ` Florian Fainelli
2026-04-10 22:11 ` Barry K. Nathan
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=20260409155821.35076-1-ojeda@kernel.org \
--to=ojeda@kernel.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 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.