From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.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@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/641] 6.18.14-rc2 review
Date: Fri, 27 Feb 2026 09:10:34 -0500 [thread overview]
Message-ID: <2026022711-unpicked-boozy-2eb6@gregkh> (raw)
In-Reply-To: <0cc404f7-f2be-4e31-bf6a-1c46e9d07b54@sirena.org.uk>
On Fri, Feb 27, 2026 at 01:47:51PM +0000, Mark Brown wrote:
> On Wed, Feb 25, 2026 at 07:51:50AM -0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.18.14 release.
> > There are 641 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>
>
> (I mentioned what looked like a regression on IRC the other day, it
> looks bogus from my investigations - just bad timing causing a flaky
> test to flake consistently everywhere I think.)
Sorry for missing that, have been traveling for conferences. And glad
to hear it was just a flake.
greg k-h
next prev parent reply other threads:[~2026-02-27 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 15:51 [PATCH 6.18 000/641] 6.18.14-rc2 review Greg Kroah-Hartman
2026-02-25 16:58 ` Peter Schneider
2026-02-25 17:07 ` Jeffrin Thalakkottoor
2026-02-25 17:34 ` Brett A C Sheffield
2026-02-25 17:48 ` Florian Fainelli
2026-02-25 21:20 ` Luna Jernberg
2026-02-25 20:09 ` Jon Hunter
2026-02-25 22:09 ` Justin Forbes
2026-02-26 19:52 ` Miguel Ojeda
2026-02-27 13:47 ` Mark Brown
2026-02-27 14:10 ` Greg Kroah-Hartman [this message]
2026-03-01 1:00 ` Guenter Roeck
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=2026022711-unpicked-boozy-2eb6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox