From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
David Woodhouse <dwmw2@infradead.org>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Robert Moore <robert.moore@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>, Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
acpica-devel@lists.linux.dev
Subject: Re: [PATCH v2 0/2] Support clean reboot after hibernate on Arm64
Date: Fri, 19 Apr 2024 16:32:58 +0100 [thread overview]
Message-ID: <171345345397.312430.3943582845307730698.b4-ty@kernel.org> (raw)
In-Reply-To: <20240412073530.2222496-1-dwmw2@infradead.org>
On Mon, 11 Mar 2024 12:19:14 +0000, David Woodhouse wrote:
> When the hardware signature in the ACPI FACS changes, the OS is supposed
> to perform a clean reboot instead of attempting to resume on a changed
> platform.
>
> Although these patches have a functional dependency, they could be merged
> separately. The second patch just won't *see* a FACS table if the ACPICA
> fix isn't present.
>
> [...]
Applied to arm64 (for-next/acpi), thanks!
[1/2] ACPICA: Detect FACS even for hardware reduced platforms
https://git.kernel.org/arm64/c/bc5b492ac305
[2/2] arm64: acpi: Honour firmware_signature field of FACS, if it exists
https://git.kernel.org/arm64/c/fbaad243b536
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2024-04-19 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 12:19 David Woodhouse
2024-03-11 12:19 ` [PATCH v2 1/2] ACPICA: Detect FACS even for hardware reduced platforms David Woodhouse
2024-03-11 13:04 ` [PATCH v2 2/2] arm64: acpi: Honour firmware_signature field of FACS, if it exists David Woodhouse
2024-04-12 14:05 ` [PATCH v2 0/2] Support clean reboot after hibernate on Arm64 Will Deacon
2024-04-12 14:18 ` David Woodhouse
2024-04-12 19:25 ` Wysocki, Rafael J
2024-04-19 15:32 ` Will Deacon [this message]
2024-04-19 15:39 ` David Woodhouse
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=171345345397.312430.3943582845307730698.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=dwmw2@infradead.org \
--cc=kernel-team@android.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=sudeep.holla@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®