From: Mathieu Chouquet-Stringer <me@mathieu.digital>
To: stable@vger.kernel.org
Cc: rafael.j.wysocki@intel.com, linux-rtc@vger.kernel.org,
linux-acpi@vger.kernel.org, rafael@kernel.org,
mgorman@techsingularity.net, gregkh@linuxfoundation.org,
alexandre.belloni@bootlin.com
Subject: Fix for rtc driver boot breakage in 6.0.y
Date: Tue, 20 Dec 2022 01:12:23 +0100 [thread overview]
Message-ID: <Y6D958DeurSuoCuY@paranoid-android> (raw)
Hello stable team and Greg,
There are 3 commits in Linus' tree for the rtc driver which should be
merged against stable 6.0.y (they're already in 6.1 / 6.1.y).
Without the first two, a x86-64 machine might panic during boot (Mel saw
a 50% chance of panic at boot - 5 out of 10 tries - and my experience
was identical).
https://lore.kernel.org/linux-acpi/20221010141630.zfzi7mk7zvnmclzy@techsingularity.net/
And after applying the first two, the kernel will not compile anymore
on non ACPI platform, so you need a third one.
The first two commits:
commit 4919d3eb2ec0ee364f7e3cf2d99646c1b224fae8
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Wed Oct 12 20:07:01 2022 +0200
rtc: cmos: Fix event handler registration ordering issue
commit 0782b66ed2fbb035dda76111df0954515e417b24
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Tue Oct 18 18:09:31 2022 +0200
rtc: cmos: Fix wake alarm breakage
And the third one:
commit db4e955ae333567dea02822624106c0b96a2f84f
Author: Alexandre Belloni <alexandre.belloni@bootlin.com>
Date: Tue Oct 18 22:35:11 2022 +0200
rtc: cmos: fix build on non-ACPI platforms
Cheers,
--
Mathieu Chouquet-Stringer me@mathieu.digital
The sun itself sees not till heaven clears.
-- William Shakespeare --
next reply other threads:[~2022-12-20 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 0:12 Mathieu Chouquet-Stringer [this message]
2022-12-21 18:21 ` Fix for rtc driver boot breakage in 6.0.y Greg KH
2022-12-23 16:59 ` Mathieu Chouquet-Stringer
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=Y6D958DeurSuoCuY@paranoid-android \
--to=me@mathieu.digital \
--cc=alexandre.belloni@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.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