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>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Ting-Han Hou <ue081723@gmail.com>
Subject: Re: [REGRESSION] 6.18.57: resume from s2idle triggers poweroff and hangs when tiny_power_button is built as a module
Date: Wed, 28 Oct 2026 15:00:02 -0400 [thread overview]
Message-ID: <20261028-rc-reply-0001-tiny-power-button-f4203@kernel.org> (raw)
In-Reply-To: <dyJyEj-TY1YtRVdDYPD4xnYF_aIP78z9wliSc3251tj6aZEZxux0c81AiZAFPpZvbg6rjgqivtHTFfY29YHTS9WZmw569IbyVF0NPVTxqrA=@proton.me>
On Wed, Oct 28, 2026 at 09:15:22 +0000, Mikkel Sejdelin wrote:
> Now that ab06eb920401 is queued for 6.18 again [1], could f4203ec64e11
> be queued with it?
Yes. ab06eb920401 stays queued for 6.18, and f4203ec64e11 ("ACPI:
tiny-power-button: Convert the driver to a platform one") is now queued
for 6.18 after it.
> Tested-by: Mikkel Sejdelin <mikkel.sejdelin@proton.me>
Thanks for testing this.
Your stack also included Ting-Han's 2/3 and 3/3. f234fdaae1ca stays
queued, and I added its upstream follow-ups edfaa81d5da5 and
7617cc05df28 as well, so the nested-resource regression (arm-cmn) that
7617cc05df28 fixed upstream does not come along.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-10-28 19:00 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
2026-10-28 9:15 ` Mikkel Sejdelin
2026-10-28 9:30 ` Thorsten Leemhuis
2026-10-28 19:00 ` Sasha Levin [this message]
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=20261028-rc-reply-0001-tiny-power-button-f4203@kernel.org \
--to=sashal@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mikkel.sejdelin@proton.me \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=ue081723@gmail.com \
/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.