From: Catalin Marinas <catalin.marinas@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH 3/3] arm64: FFH: Move ACPI specific code into drivers/acpi/arm64/
Date: Tue, 11 Jun 2024 17:54:24 +0100 [thread overview]
Message-ID: <ZmiBQC05N_YUzcYk@arm.com> (raw)
In-Reply-To: <20240605131458.3341095-4-sudeep.holla@arm.com>
On Wed, Jun 05, 2024 at 02:14:58PM +0100, Sudeep Holla wrote:
> The ACPI FFH Opregion code can be moved out of arm64 arch code as
> it just uses SMCCC. Move all the ACPI FFH Opregion code into
> drivers/acpi/arm64/ffh.c
>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH 3/3] arm64: FFH: Move ACPI specific code into drivers/acpi/arm64/
Date: Tue, 11 Jun 2024 17:54:24 +0100 [thread overview]
Message-ID: <ZmiBQC05N_YUzcYk@arm.com> (raw)
In-Reply-To: <20240605131458.3341095-4-sudeep.holla@arm.com>
On Wed, Jun 05, 2024 at 02:14:58PM +0100, Sudeep Holla wrote:
> The ACPI FFH Opregion code can be moved out of arm64 arch code as
> it just uses SMCCC. Move all the ACPI FFH Opregion code into
> drivers/acpi/arm64/ffh.c
>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-06-11 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 13:14 [PATCH 0/3] ACPI: arm64: some cleanups Sudeep Holla
2024-06-05 13:14 ` Sudeep Holla
2024-06-05 13:14 ` [PATCH 1/3] ACPI: arm64: Sort entries alphabetically Sudeep Holla
2024-06-05 13:14 ` Sudeep Holla
2024-06-05 13:14 ` [PATCH 2/3] arm64: cpuidle: Move ACPI specific code into drivers/acpi/arm64/ Sudeep Holla
2024-06-05 13:14 ` Sudeep Holla
2024-06-11 16:54 ` Catalin Marinas
2024-06-11 16:54 ` Catalin Marinas
2024-06-13 2:21 ` Hanjun Guo
2024-06-05 13:14 ` [PATCH 3/3] arm64: FFH: " Sudeep Holla
2024-06-05 13:14 ` Sudeep Holla
2024-06-11 16:54 ` Catalin Marinas [this message]
2024-06-11 16:54 ` Catalin Marinas
2024-06-13 2:19 ` [PATCH 0/3] ACPI: arm64: some cleanups Hanjun Guo
2024-06-13 9:50 ` Catalin Marinas
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=ZmiBQC05N_YUzcYk@arm.com \
--to=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@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.