From: Jeremy Linton <jeremy.linton@arm.com>
To: Jose Marinho <jose.marinho@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
James Morse <James.Morse@arm.com>,
Rob Herring <Rob.Herring@arm.com>, Will Deacon <will@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Hanjun Guo <guohanjun@huawei.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/3 v2] Update ACPI documentation for Arm systems
Date: Tue, 6 Jun 2023 18:54:35 -0500 [thread overview]
Message-ID: <888baa97-ac71-18ca-ad21-eae19ef241f1@arm.com> (raw)
In-Reply-To: <20230606093528.1494344-1-jose.marinho@arm.com>
Hi,
On 6/6/23 04:35, Jose Marinho wrote:
> This set of patches updates the Linux kernel ACPI documentation for Arm
> systems. The intent is to integrate the developments in the BBR
> specification that happened over the last couple of years.
Thanks for doing this, it has been sorely needed. The changes all look
good to me too, so:
Reviewed-by: Jeremy Linton <jeremy.linton@arm.com>
Now all that said, at some point it will be worthwhile to reopen the
discussion around a few of the more "controversial" parts of this
document so they better reflect the current state of machines utilizing
ACPI.
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Jeremy Linton <Jeremy.Linton@arm.com>
> Cc: James Morse <James.Morse@arm.com>
> Cc: Rob Herring <Rob.Herring@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Hanjun Guo <guohanjun@huawei.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-doc@vger.kernel.org
> Cc: linux-acpi@vger.kernel.org
>
> v2:
> - Clarify that the RAS tables are conditionaly required when ACPI
> Platform Error Interfaces are required: Hanjun Guo.
> - Clarify that HMAT is required if NUMA is supported and the system
> contains heterogeneous memory: Hanjun Guo.
>
>
> Jose Marinho (3):
> Documentation/arm64: Update ARM and arch reference
> Documentation/arm64: Update references in arm-acpi
> Documentation/arm64: Update ACPI tables from BBR
>
> Documentation/arm64/acpi_object_usage.rst | 81 ++++++++++-
> Documentation/arm64/arm-acpi.rst | 168 ++++++++++++++--------
> 2 files changed, 183 insertions(+), 66 deletions(-)
>
next prev parent reply other threads:[~2023-06-06 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 9:35 [PATCH 0/3 v2] Update ACPI documentation for Arm systems Jose Marinho
2023-06-06 9:35 ` [PATCH 1/3 v2] Documentation/arm64: Update ARM and arch reference Jose Marinho
2023-06-06 11:50 ` Robin Murphy
2023-06-19 12:22 ` Wilczynski, Michal
2023-06-20 6:51 ` Hanjun Guo
2023-06-06 9:35 ` [PATCH 2/3 v2] Documentation/arm64: Update references in arm-acpi Jose Marinho
2023-06-06 11:56 ` Robin Murphy
2023-06-06 9:35 ` [PATCH 3/3 v2] Documentation/arm64: Update ACPI tables from BBR Jose Marinho
2023-06-06 13:37 ` [PATCH 0/3 v2] Update ACPI documentation for Arm systems Sudeep Holla
2023-06-06 23:54 ` Jeremy Linton [this message]
2023-06-07 11:02 ` Hanjun Guo
2023-06-14 17:18 ` 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=888baa97-ac71-18ca-ad21-eae19ef241f1@arm.com \
--to=jeremy.linton@arm.com \
--cc=James.Morse@arm.com \
--cc=Rob.Herring@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=guohanjun@huawei.com \
--cc=jose.marinho@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox