From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@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,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com
Subject: Re: [PATCH 6.14 00/21] 6.14.1-rc1 review
Date: Fri, 4 Apr 2025 13:01:52 +0100 [thread overview]
Message-ID: <3aa766cc-5db3-4ce9-a2a8-e4ec105ff77e@sirena.org.uk> (raw)
In-Reply-To: <20250403151621.130541515@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
On Thu, Apr 03, 2025 at 04:20:04PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.14.1 release.
> There are 21 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: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-04 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 15:20 Greg Kroah-Hartman
2025-04-03 17:00 ` Ronald Warsow
2025-04-03 19:53 ` Peter Schneider
2025-04-04 10:18 ` Luna Jernberg
2025-04-04 13:28 ` Luna Jernberg
2025-04-04 10:38 ` Christian Heusel
2025-04-04 12:01 ` Mark Brown [this message]
2025-04-04 13:20 ` Takeshi Ogasawara
2025-04-04 13:58 ` Naresh Kamboju
2025-04-04 14:44 ` Shuah Khan
2025-04-04 17:01 ` Florian Fainelli
2025-04-04 19:32 ` Jon Hunter
2025-04-04 20:08 ` Frank Scheiner
2025-04-04 21:38 ` Justin Forbes
2025-04-05 2:03 ` Ron Economos
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=3aa766cc-5db3-4ce9-a2a8-e4ec105ff77e@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®