From: Sasha Levin <sashal@kernel.org>
To: Mikkel Sejdelin <mikkel.sejdelin@proton.me>
Cc: Sasha Levin <sashal@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"rafael@kernel.org" <rafael@kernel.org>
Subject: Re: [REGRESSION] 6.18.57: resume from s2idle triggers poweroff and hangs when tiny_power_button is built as a module
Date: Sat, 24 Oct 2026 10:26:52 -0400 [thread overview]
Message-ID: <20261024-rc-reply-0001-tiny-power-button-s2idle@kernel.org> (raw)
In-Reply-To: <1kU98bgDqqEMGUcpGahaBYlaPiP2ssSCZj1uIKq1MEaGpNv2exGeJc3VWzXxB8-VJQ1Uk62W19oByt2KC-v1bSA4Sux9fBhnlA_IHWjV2Zw=@proton.me>
> Suggested fix: backport f4203ec64e11 together with 52d864019636, or
> revert 38c79dacc806 (and its dependents) from 6.18.y. Note that the same
I have dropped f4203ec64e11 ("ACPI: tiny-power-button: Convert the
driver to a platform one") from the 6.18 queue. It cannot go out without
ab06eb920401 ("ACPI: scan: Register platform devices for fixed event
buttons"): on its own it would break tiny-power-button on systems with a
fixed-hardware power button. Greg dropped ab06eb920401 on October 23,
together with two ACPI resource-overlap patches that broke the 6.18
build, so it is not part of this release either.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-24 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 8:35 [REGRESSION] 6.18.57: resume from s2idle triggers poweroff and hangs when tiny_power_button is built as a module Mikkel Sejdelin
2026-10-21 13:53 ` Thorsten Leemhuis
2026-10-21 16:44 ` Sv: " Mikkel Sejdelin
2026-10-22 2:03 ` Sasha Levin
2026-10-24 14:26 ` Sasha Levin [this message]
2026-10-28 9:15 ` Mikkel Sejdelin
2026-10-28 9:30 ` Thorsten Leemhuis
2026-10-28 19:00 ` Sasha Levin
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=20261024-rc-reply-0001-tiny-power-button-s2idle@kernel.org \
--to=sashal@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mikkel.sejdelin@proton.me \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.