From: Al Stone <ahs3@redhat.com>
To: Al Stone <al.stone@linaro.org>,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: linaro-acpi@lists.linaro.org, patches@linaro.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version
Date: Mon, 2 May 2016 14:19:32 -0600 [thread overview]
Message-ID: <3b6d5be3-40ab-94dc-2590-8b2638cbdc15@redhat.com> (raw)
In-Reply-To: <1461619287-27211-1-git-send-email-al.stone@linaro.org>
On 04/25/2016 03:21 PM, Al Stone wrote:
> The ACPI 6.1 specification was recently released at the end of January
> 2016, but the arm64 kernel documentation for the use of ACPI was written
> for the 5.1 version of the spec. There were significant additions to the
> spec that had not yet been mentioned -- for example, the 6.0 mechanisms
> added to make it easier to define processors and low power idle states,
> as well as the 6.1 addition allowing regular interrupts (not just from
> GPIO) be used to signal ACPI general purpose events.
>
> This patch reflects going back through and examining the specs in detail
> and updating content appropriately. Whilst there, a few odds and ends of
> typos were caught as well. This brings the documentation up to date with
> ACPI 6.1 for arm64.
>
> Changes for v5:
> -- Miscellaneous typos and corrections (Lorenzo Pieralisi)
> -- Add linux-acpi@ ML to the distribution list (Alexey Klimov)
> -- Corrections to CPPC information (Alexey Klimov)
> -- ACK from Lorenzo Pieralisi
> -- Updated bibliographic info (Al Stone)
>
> Changes for v4:
> -- Clarify that IORT can sometimes be optional (Jon Masters).
> -- Remove "Use as needed" descriptions of ACPI objects; they provide
> no substantive information and doing so simplifies maintenance of
> this document over time. These have been replaced with a simpler
> notice that states that unless otherwise noted, do what the ACPI
> specification says is needed.
> -- Corrected the _OSI object usage recommendation; it described kernel
> behavior that does not exist (Al Stone).
>
> Changes for v3:
> -- Clarify use of _LPI/_RDI (Vikas Sajjan)
> -- Whitespace cleanup as pointed out by checkpatch
>
> Changes for v2:
> -- Clean up white space (Harb Abdulhahmid)
> -- Clarification on _CCA usage (Harb Abdulhamid)
> -- IORT moved to required from recommended (Hanjun Guo)
> -- Clarify IORT description (Hanjun Guo)
>
>
> Al Stone (1):
> ARM64: ACPI: Update documentation for latest specification version
>
> Documentation/arm64/acpi_object_usage.txt | 343 ++++++++++++++++--------------
> Documentation/arm64/arm-acpi.txt | 40 ++--
> 2 files changed, 213 insertions(+), 170 deletions(-)
>
Ping? If there are no further comments, can this be pulled in through
either the documentation or arm64 tree?
Thanks.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
next prev parent reply other threads:[~2016-05-02 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 21:21 Al Stone
2016-04-25 21:21 ` [PATCH v5 1/1] " Al Stone
2016-05-13 1:48 ` Hanjun Guo
2016-05-02 20:19 ` Al Stone [this message]
2016-05-12 21:30 ` [PATCH v5 0/1] " Roy Franz (HPE)
2016-05-16 23:44 ` Alexey Klimov
2016-05-17 16:30 ` Al Stone
2016-05-26 22:31 ` Al Stone
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=3b6d5be3-40ab-94dc-2590-8b2638cbdc15@redhat.com \
--to=ahs3@redhat.com \
--cc=al.stone@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.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
all inboxes | Powered by JetHome®