From: Esben Haabendal <esben@geanix.com>
To: "Thorsten Leemhuis" <regressions@leemhuis.info>
Cc: "alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"Nick Bowler" <nbowler@draconx.ca>,
"Anthony Pighin (Nokia)" <anthony.pighin@nokia.com>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [PATCH] rtc: interface: Alarm race handling should not discard preceding error
Date: Fri, 09 Jan 2026 13:54:26 +0100 [thread overview]
Message-ID: <87o6n3c5fh.fsf@geanix.com> (raw)
In-Reply-To: <45d14eb4-9495-4aa8-9382-8d756c0ae39e@leemhuis.info> (Thorsten Leemhuis's message of "Fri, 09 Jan 2026 13:18:29 +0100")
"Thorsten Leemhuis" <regressions@leemhuis.info> writes:
> On 12/16/25 16:09, Nick Bowler wrote:
>> On Tue, Dec 16, 2025 at 11:51:30AM +0100, Thorsten Leemhuis wrote:
>>> Lo! FWIW, Nick Bowler (now CCed) reported that below patch fixes a
>>> regression for him caused by the commit from Esben (now also CCed) the
>>> Fixes: tag mentions. See "hwclock busted w/ M48T59 RTC (regression)" for
>>> details:
>>> https://lore.kernel.org/all/2t6bhs4udbu55ctbemkhlluchz2exrwown7kmu2gss6zukaxdm@ughygemahmem/
>>> and
>>>
>>> Nick, could you maybe provide a tested-by tag here? Maybe that would
>>> motivate someone to get this en route to mainline.
>>>
>>> Adding a "Cc: <stable@vger.kernel.org>" would be great, too, as Nick
>>> encountered this on earlier series, as it was backported all the way to
>>> 5.15.y
>>
>> It was backported to 5.10.y and 5.4.y too, but only after I had reported
>> this regression back in October (and I guess 5.4.y is EOL now).
>>
>> Tested-by: Nick Bowler <nbowler@draconx.ca>
>
> Esben (author of the culprit) and Alexandre (who merged it): do you
> still have reviewing/applying the patch at the start of this thread (
> https://lore.kernel.org/all/BN0PR08MB6951415A751F236375A2945683D1A@BN0PR08MB6951.namprd08.prod.outlook.com/#t)
> on your todo list?
>
> Sorry for nagging, would just be good to finally get this 6.18-rc1
> regression fixed in mainline so the fix can be backported to stable,
> too. And due to the holidays I thought a quick reminder might be wise.
>
> Or was this fixed somehow and I just missed it?
Sorry for introducing this error. The fix looks good to me. I have added
my Reviewed-by to it.
Am I correct in that it also fixes the problem reported by Nick Bowler?
/Esben
next prev parent reply other threads:[~2026-01-09 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 17:35 [PATCH] rtc: interface: Alarm race handling should not discard preceding error Anthony Pighin (Nokia)
2025-12-16 10:51 ` Thorsten Leemhuis
2025-12-16 15:09 ` Nick Bowler
2026-01-09 12:18 ` Thorsten Leemhuis
2026-01-09 12:54 ` Esben Haabendal [this message]
2026-01-09 13:04 ` Thorsten Leemhuis
2026-01-09 12:50 ` Esben Haabendal
2026-01-19 23:08 ` Alexandre Belloni
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=87o6n3c5fh.fsf@geanix.com \
--to=esben@geanix.com \
--cc=alexandre.belloni@bootlin.com \
--cc=anthony.pighin@nokia.com \
--cc=linux-rtc@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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