linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version
Date: Mon, 18 Apr 2016 10:07:08 +0100	[thread overview]
Message-ID: <20160418090708.GA2427@red-moon> (raw)
In-Reply-To: <57112AC0.2050607@linaro.org>

On Fri, Apr 15, 2016 at 11:54:08AM -0600, Al Stone wrote:

[...]

> > Understood, the point I wanted to make is that adding a list of methods
> > in acpi_object_usage.txt ("Use as needed") is not necessarily additional
> > information, you can add a pointer at ACPI specs (for that specific
> > purpose - as I said there are parts of the patch that add additional
> > information Linux related) for that purpose instead of having to list
> > all of them in acpi_object_usage.txt again.
> 
> I see.  That makes sense.  How about I collapse those down with something
> on the order of "unless otherwise noted, use as needed" and just remove the
> ones that have no specific info?

Agreed, that would also help you avoid keeping track of new specs
updates that do not necessarily require updates to these docs.

Lorenzo

  reply	other threads:[~2016-04-18  9:07 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 [this message]
2016-04-15 21:35 ` Jonathan Corbet
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=20160418090708.GA2427@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).