linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Al Stone <al.stone@linaro.org>
Cc: linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linaro-acpi@lists.linaro.org,
	patches@linaro.org, linaro-kernel@lists.linaro.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version
Date: Fri, 15 Apr 2016 15:35:51 -0600	[thread overview]
Message-ID: <20160415153551.4054d360@lwn.net> (raw)
In-Reply-To: <1459210002-3387-1-git-send-email-al.stone@linaro.org>

On Mon, 28 Mar 2016 18:06:42 -0600
Al Stone <al.stone@linaro.org> wrote:

> 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.

So I'll happily pull this into the docs tree if that seems like the right
place for it.  I'd really like to see an ack or two first, though, since
I'm not really in a position to review it properly myself.

Thanks,

jon

  parent reply	other threads:[~2016-04-15 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29  0:06 [PATCH v3] ARM64: ACPI: Update documentation for latest specification version Al Stone
2016-04-07 21:50 ` Al Stone
2016-04-08 13:12   ` Will Deacon
2016-04-08 14:28     ` Al Stone
2016-04-11  2:12 ` Hanjun Guo
2016-04-15 14:37 ` Lorenzo Pieralisi
2016-04-15 16:41   ` Al Stone
2016-04-15 17:47     ` Lorenzo Pieralisi
2016-04-15 17:54       ` Al Stone
2016-04-18  9:07         ` Lorenzo Pieralisi
2016-04-15 21:35 ` Jonathan Corbet [this message]
2016-04-15 21:58   ` Al Stone
2016-04-18  2:58 ` Jon Masters

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=20160415153551.4054d360@lwn.net \
    --to=corbet@lwn.net \
    --cc=al.stone@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).