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@denx.de,
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.6 000/529] 6.6.117-rc1 review
Date: Sun, 23 Nov 2025 00:31:41 +0100 [thread overview]
Message-ID: <20251122233141.1722084-1-ojeda@kernel.org> (raw)
In-Reply-To: <20251121130230.985163914@linuxfoundation.org>
On Fri, 21 Nov 2025 14:04:59 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.6.117 release.
> There are 529 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 Sun, 23 Nov 2025 13:01:08 +0000.
> Anything received after that time might be too late.
Boot-tested under QEMU for Rust x86_64:
Tested-by: Miguel Ojeda <ojeda@kernel.org>
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-11-22 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 13:04 [PATCH 6.6 000/529] 6.6.117-rc1 review Greg Kroah-Hartman
2025-11-21 16:28 ` Jon Hunter
2025-11-21 18:12 ` Florian Fainelli
2025-11-22 4:51 ` Naresh Kamboju
2025-11-22 5:53 ` Brett A C Sheffield
2025-11-22 7:12 ` Peter Schneider
2025-11-22 11:17 ` Ron Economos
2025-11-22 23:31 ` Miguel Ojeda [this message]
2025-11-23 11:54 ` 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=20251122233141.1722084-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@denx.de \
--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