[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025060406-dial-boxlike-7e57@gregkh>
Date: Wed, 4 Jun 2025 10:09:04 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Mark Brown <broonie@...nel.org>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
jonathanh@...dia.com, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
conor@...nel.org, hargar@...rosoft.com
Subject: Re: [PATCH 5.10 000/270] 5.10.238-rc1 review
On Tue, Jun 03, 2025 at 11:46:06AM +0100, Mark Brown wrote:
> On Tue, Jun 03, 2025 at 12:06:34PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Jun 03, 2025 at 10:45:34AM +0100, Mark Brown wrote:
>
> > > This fails to boot with a NFS root on Raspberry Pi 3b+, due to
> > > 558a48d4fabd70213117ec20f476adff48f72365 ("net: phy: microchip: force
> > > IRQ polling mode for lan88xx") as was also a problem for other stables.
>
> > Odd, I see it in the 5.15.y released tree, so did we get a fix for it
> > with a different commit or should it just be dropped entirely from the
> > 5.10.y queue?
>
> There's a revert in the v5.15 tree as 2edc296e2107a003e383f87cdc7e29bddcb6b17e,
> IIRC it went it while I was on holiday so I didn't test the release it
> went into.
Ah, that makes sense. All now dropped, thanks for warning me.
greg k-h
Powered by blists - more mailing lists