From: Francesco Dolcini <francesco@dolcini.it>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
gregkh@linuxfoundation.org, patches@lists.linux.dev,
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 6.6 000/684] 6.6.128-rc2 review
Date: Tue, 3 Mar 2026 08:36:46 +0100 [thread overview]
Message-ID: <20260303073646.GB9569@francesco-nb> (raw)
In-Reply-To: <20260302160934.2521545-1-sashal@kernel.org>
On Mon, Mar 02, 2026 at 11:09:34AM -0500, Sasha Levin wrote:
>
> This is the start of the stable review cycle for the 6.6.128 release.
> There are 684 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.
Compiled and tested on
- Verdin iMX8MM
- Colibri iMX6
- Apalis iMX6
- Colibri iMX6ULL
- Colibri iMX7
Tested-by: Francesco Dolcini <francesco.dolcini@toradex.com>
next prev parent reply other threads:[~2026-03-03 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:09 [PATCH 6.6 000/684] 6.6.128-rc2 review Sasha Levin
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-04 7:41 ` Brett A C Sheffield
2026-03-04 12:14 ` Sasha Levin
2026-03-04 13:29 ` Brett A C Sheffield
2026-03-02 21:58 ` Peter Schneider
2026-03-03 5:01 ` Florian Fainelli
2026-03-03 7:36 ` Francesco Dolcini [this message]
2026-03-03 8:22 ` Shung-Hsi Yu
2026-03-03 12:20 ` Ron Economos
2026-03-03 14:12 ` Jon Hunter
2026-03-03 19:19 ` Mark Brown
2026-03-03 19:33 ` Shuah Khan
2026-03-03 21:21 ` Miguel Ojeda
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=20260303073646.GB9569@francesco-nb \
--to=francesco@dolcini.it \
--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=sashal@kernel.org \
--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.