public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	gregkh@linuxfoundation.org, patches@lists.linux.dev,
	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, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com
Subject: Re: [PATCH 5.10 000/334] 5.10.252-rc2 review
Date: Sat, 7 Mar 2026 08:20:55 -0500	[thread overview]
Message-ID: <aawmN6mkFZnv0Nd3@laps> (raw)
In-Reply-To: <992df439ca66e562353d285642c6ab8e1c69e2e6.camel@decadent.org.uk>

On Fri, Mar 06, 2026 at 08:19:01PM +0100, Ben Hutchings wrote:
>On Mon, 2026-03-02 at 11:10 -0500, Sasha Levin wrote:
>> This is the start of the stable review cycle for the 5.10.252 release.
>> There are 334 patches in this series, all will be posted as a response
>> to this one.
>
>And yet they were not.

I don't think we ever did post the series for -rc2+, did we?

I guess I need to remove the message...

>> If anyone has any issues with these being applied, please
>> let me know.
>
>I can some issues, such as these feature additions being backported:
>
>[...]
>> Rui Feng (1):
>>   misc: rtsx: Add SD Express mode support for RTS5261
>[...]
>> Ulf Hansson (1):
>>   mmc: core: Initial support for SD express card/host
>[...]
>
>supposedly as dependencies of:
>
>> Matthew Schwartz (1):
>>   mmc: rtsx_pci_sdmmc: increase power-on settling delay to 5ms
>
>But it doesn't depend on them.  And it also got reverted in this same
>series.  So backporting the "dependencies" just introduced risk with no
>benefit.
>
>Meanwhile, the stable-specific regressions in recent 5.10.y stable
>releases (affecting ARM memset64() and IPv6 tunnels) were not addressed
>in 5.10.252.

Thanks for the heads-up, I've queued up both fixes.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-03-07 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 16:10 [PATCH 5.10 000/334] 5.10.252-rc2 review Sasha Levin
2026-03-02 18:35 ` Florian Fainelli
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-02 20:16 ` Woody Suwalski
2026-03-03 14:12 ` Jon Hunter
2026-03-03 19:42 ` Mark Brown
2026-03-04  1:33 ` Barry K. Nathan
2026-03-06 19:19 ` Ben Hutchings
2026-03-07 13:20   ` Sasha Levin [this message]
2026-03-08 10:26     ` Ben Hutchings
2026-03-08 17:55       ` Sasha Levin
2026-03-26 13:13 ` Ben Hutchings

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=aawmN6mkFZnv0Nd3@laps \
    --to=sashal@kernel.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=broonie@kernel.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@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