From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, 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, broonie@kernel.org
Subject: Re: [PATCH 6.12 000/413] 6.12.35-rc2 review
Date: Sun, 6 Jul 2025 08:03:56 +0200 [thread overview]
Message-ID: <2025070613-escalate-action-761d@gregkh> (raw)
In-Reply-To: <3037c3e6-558b-4824-8c78-a36990f4e4d6@roeck-us.net>
On Sat, Jul 05, 2025 at 12:37:52PM -0700, Guenter Roeck wrote:
> Hi Greg,
>
> On Tue, Jun 24, 2025 at 01:29:53PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.12.35 release.
> > There are 413 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 Thu, 26 Jun 2025 12:13:28 +0000.
> > Anything received after that time might be too late.
> >
>
> Some subsequent fixes are missing:
>
> > Tzung-Bi Shih <tzungbi@kernel.org>
> > drm/i915/pmu: Fix build error with GCOV and AutoFDO enabled
> >
>
> Fixed by commit d02b2103a08b ("drm/i915: fix build error some more").
How did you check? This is already in the queues for 6.6, 6.12, and
6.15.
> > Shyam Prasad N <sprasad@microsoft.com>
> > cifs: do not disable interface polling on failure
> >
>
> Fixed by commit 3bbe46716092 ("smb: client: fix warning when reconnecting
> channel") in linux-next (not yet in mainline as of right now).
Not in a release yet.
> > Jens Axboe <axboe@kernel.dk>
> > io_uring/kbuf: don't truncate end buffer for multiple buffer peeks
> >
>
> Fixed by commit 9a709b7e98e6 ("io_uring/net: mark iov as dynamically
> allocated even for single segments") and commit 178b8ff66ff8 ("io_uring/kbuf:
> flag partial buffer mappings").
Both are alread in 6.12 and 6.15 queues
> > Yong Wang <yongwang@nvidia.com>
> > net: bridge: mcast: re-implement br_multicast_{enable, disable}_port functions
> >
>
> Fixed by commit 7544f3f5b0b5 ("bridge: mcast: Fix use-after-free during
> router port configuration").
Already in the 6.15 queue
> > Niklas Cassel <cassel@kernel.org>
> > ata: ahci: Disallow LPM for ASUSPRO-D840SA motherboard
> >
>
> Fixed by commit 3e0809b1664b ("ata: ahci: Use correct DMI identifier
> for ASUSPRO-D840SA LPM quirk").
Already in the 6.12 and 6.15 queues.
> I assume the missing fixes will be queued in one of the next LTS releases.
They are going to be in THIS release, with one exception as noted above.
I think something went really wrong with your checking scripts :(
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-06 6:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 12:29 [PATCH 6.12 000/413] 6.12.35-rc2 review Greg Kroah-Hartman
2025-06-24 14:43 ` Peter Schneider
2025-06-24 17:30 ` Florian Fainelli
2025-06-25 7:24 ` Jon Hunter
2025-06-25 10:23 ` Naresh Kamboju
2025-06-25 14:31 ` Brett Mastbergen
2025-06-25 18:51 ` Pavel Machek
2025-06-25 19:56 ` Mark Brown
2025-06-25 23:09 ` Miguel Ojeda
2025-07-05 19:37 ` Guenter Roeck
2025-07-06 6:03 ` Greg Kroah-Hartman [this message]
2025-07-07 20:48 ` 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=2025070613-escalate-action-761d@gregkh \
--to=gregkh@linuxfoundation.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@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;
as well as URLs for NNTP newsgroup(s).