[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2t6bhs4udbu55ctbemkhlluchz2exrwown7kmu2gss6zukaxdm@ughygemahmem>
Date: Sun, 14 Dec 2025 17:04:41 -0500
From: Nick Bowler <nbowler@...conx.ca>
To: Thorsten Leemhuis <regressions@...mhuis.info>
Cc: linux-kernel@...r.kernel.org, regressions@...ts.linux.dev,
linux-rtc@...r.kernel.org, Esben Haabendal <esben@...nix.com>, stable@...r.kernel.org,
sparclinux@...r.kernel.org
Subject: Re: PROBLEM: hwclock busted w/ M48T59 RTC (regression)
On Mon, Dec 08, 2025 at 03:35:42PM +0100, Thorsten Leemhuis wrote:
> Lo!
>
> On 11/26/25 04:18, Nick Bowler wrote:
> > Any thoughts?
>
> Not really, just a vague idea (and reminder, this is not my area or
> expertise, I'm just tracking regressions):
>
> Two fixes were proposed for the culprit, see:
>
> https://lore.kernel.org/all/BN0PR08MB69510928028C933749F4139383D1A@BN0PR08MB6951.namprd08.prod.outlook.com/
> https://lore.kernel.org/all/BN0PR08MB6951415A751F236375A2945683D1A@BN0PR08MB6951.namprd08.prod.outlook.com/
The first link is a patch for a totally different driver, as far as I
know not relevant to any system I have, but I guess that makes at least
3 different systems which have regressed...
I can't figure out how to turn the second link into a correctly-
formatted patch file, but since it is a one-line change I just manually
applied it on top of 6.19-rc1. This appears to fix the problem.
Thanks,
Nick
Powered by blists - more mailing lists