Date: Mon, 18 Apr 2016 10:07:08 +0100
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
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>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v3] ARM64: ACPI: Update documentation for latest
 specification version
Message-ID: <20160418090708.GA2427@red-moon>
References: <1459210002-3387-1-git-send-email-al.stone@linaro.org>
 <20160415143719.GA8798@red-moon>
 <5711199E.9010508@linaro.org>
 <20160415174716.GB10014@red-moon>
 <57112AC0.2050607@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <57112AC0.2050607@linaro.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 817
Lines: 19

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