From: Conor Dooley <conor@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@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, florian.fainelli@broadcom.com,
pavel@denx.de
Subject: Re: [PATCH 6.7 000/707] 6.7.11-rc2 review
Date: Tue, 26 Mar 2024 19:52:32 +0000 [thread overview]
Message-ID: <20240326-skydiver-maybe-2e7a2335aef3@spud> (raw)
In-Reply-To: <20240325120003.1767691-1-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Mon, Mar 25, 2024 at 08:00:03AM -0400, Sasha Levin wrote:
>
> This is the start of the stable review cycle for the 6.7.11 release.
> There are 707 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.
Tested-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-26 19:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:00 [PATCH 6.7 000/707] 6.7.11-rc2 review Sasha Levin
2024-03-25 17:43 ` Daniel Díaz
2024-03-25 18:14 ` Sami Tolvanen
2024-03-25 19:47 ` Daniel Díaz
2024-03-26 11:23 ` Sasha Levin
2024-03-25 17:57 ` SeongJae Park
2024-03-25 18:22 ` Naresh Kamboju
2024-03-25 19:07 ` Pavel Machek
2024-03-25 20:05 ` Justin Forbes
2024-03-25 20:39 ` Florian Fainelli
2024-03-26 2:09 ` Bagas Sanjaya
2024-03-26 9:04 ` Ron Economos
2024-03-26 16:16 ` Mark Brown
2024-03-26 17:28 ` Greg KH
2024-03-26 17:35 ` Mark Brown
2024-03-26 17:00 ` Shuah Khan
2024-03-26 19:52 ` Conor Dooley [this message]
2024-03-26 20:48 ` Shreeya Patel
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=20240326-skydiver-maybe-2e7a2335aef3@spud \
--to=conor@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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