From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
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, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/430] 6.18.3-rc1 review
Date: Tue, 30 Dec 2025 13:12:54 +0100 [thread overview]
Message-ID: <2025123013-smilingly-vixen-783f@gregkh> (raw)
In-Reply-To: <6acaaac9-f7bd-4696-859f-c0d491a0ea14@t-8ch.de>
On Tue, Dec 30, 2025 at 12:58:08PM +0100, Thomas Weißschuh wrote:
> Hi Greg,
>
> On 2025-12-29 17:06:42+0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.18.3 release.
> > There are 430 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 Wed, 31 Dec 2025 16:06:10 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.18.3-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.18.y
> > and the diffstat can be found below.
>
> I am missing commit 4dbf066d965c ("leds: leds-cros_ec: Skip LEDs without
> color components"). This commit is in Linus' tree, has a stable tag and
> also I requested it's backport in [0].
>
> Did I mess up or did it fall through the cracks?
> Any chance to get it included in the next batch of stable releases?
It's still pending, I have 200+ patches left to go through. The big
-rc1 merge combined with the holidays caused the backup, sorry.
Hopefully will dig out from that during the beginning of January.
thanks,
greg k-h
next prev parent reply other threads:[~2025-12-30 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 16:06 [PATCH 6.18 000/430] 6.18.3-rc1 review Greg Kroah-Hartman
2025-12-29 16:32 ` Brett A C Sheffield
2025-12-29 21:02 ` Ronald Warsow
2025-12-30 1:24 ` Takeshi Ogasawara
2025-12-30 11:47 ` Ron Economos
2025-12-30 11:58 ` Thomas Weißschuh
2025-12-30 12:12 ` Greg Kroah-Hartman [this message]
2025-12-30 14:39 ` Peter Schneider
2025-12-30 14:59 ` Justin Forbes
2025-12-30 15:21 ` Naresh Kamboju
2025-12-30 15:38 ` Jeffrin Thalakkottoor
2025-12-30 19:29 ` Dileep malepu
2025-12-31 1:09 ` Miguel Ojeda
2025-12-31 16:42 ` Florian Fainelli
2026-01-02 10:13 ` Jon Hunter
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=2025123013-smilingly-vixen-783f@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=linux@weissschuh.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