public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, heikki.krogerus@linux.intel.com,
	rafael@kernel.org,
	/tmp/small/0000-cover-letter.patch@punajuuri.localdomain
Subject: Re: [PATCH 4/7] Documentation: ACPI: Update references
Date: Tue, 30 Nov 2021 17:57:58 +0200	[thread overview]
Message-ID: <YaZKBpJi2C/R/6VO@smile.fi.intel.com> (raw)
In-Reply-To: <20211130153250.935726-4-sakari.ailus@linux.intel.com>

On Tue, Nov 30, 2021 at 05:32:47PM +0200, Sakari Ailus wrote:
> Update references for the ACPI _DSD documentation. In particular:
> 
> - Substitute _DSD property and hierarchical data extension documents with
>   the newer DSD guide that replaces both, and use its HTML form.
> 
> - Refer to the latest ACPI spec.
> 
> - Add data node reference documentation reference to graph documentation.

...

> -[1] _DSD (Device Specific Data) Implementation Guide.
> -    https://www.uefi.org/sites/default/files/resources/_DSD-implementation-guide-toplevel-1_1.htm,
> -    referenced 2016-10-03.
> +[1] Devicetree. https://www.devicetree.org, referenced 2016-10-03.
>  
> -[2] Devicetree. https://www.devicetree.org, referenced 2016-10-03.
> +[2] Common bindings for device graphs (Devicetree).
> +    https://github.com/devicetree-org/dt-schema/blob/main/schemas/graph.yaml,
> +    referenced 2021-11-30.
>  
> -[3] Documentation/devicetree/bindings/graph.txt
> +[3] DSD Guide. https://github.com/UEFI/DSD-Guide/blob/main/dsd-guide.adoc,
> +    referenced 2021-11-30.
>  
> -[4] Device Properties UUID For _DSD.
> -    https://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf,
> -    referenced 2016-10-04.
> +[4] Advanced Configuration and Power Interface Specification.
> +    https://uefi.org/specifications/ACPI/6.4/, referenced 2021-11-30.
>  
> -[5] Hierarchical Data Extension UUID For _DSD.
> -    https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf,
> -    referenced 2016-10-04.
> -
> -[6] Advanced Configuration and Power Interface Specification.
> -    https://www.uefi.org/sites/default/files/resources/ACPI_6_1.pdf,
> -    referenced 2016-10-04.
> -
> -[7] _DSD Device Properties Usage Rules.
> +[5] _DSD Device Properties Usage Rules.
>      Documentation/firmware-guide/acpi/DSD-properties-rules.rst
> +
> +[6] Documentation/firmware-guide/acpi/dsd/data-node-references.rst

To make this patch shorter and any improvements cleaner in the future can you
use labeled references instead of numbered? This will reduce a lot of churn.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-11-30 15:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 15:32 [PATCH 1/7] device property: Fix fwnode_graph_devcon_match() fwnode leak Sakari Ailus
2021-11-30 15:32 ` [PATCH 2/7] device property: Fix documentation for FWNODE_GRAPH_DEVICE_DISABLED Sakari Ailus
2021-11-30 15:32 ` [PATCH 3/7] Documentation: ACPI: Fix data node reference documentation Sakari Ailus
2021-11-30 15:55   ` Andy Shevchenko
2021-11-30 20:42     ` Sakari Ailus
2021-11-30 20:50       ` Rafael J. Wysocki
2021-11-30 15:32 ` [PATCH 4/7] Documentation: ACPI: Update references Sakari Ailus
2021-11-30 15:57   ` Andy Shevchenko [this message]
2021-11-30 15:32 ` [PATCH 5/7] device property: Implement fwnode_graph_get_endpoint_count() Sakari Ailus
2021-11-30 16:01   ` Andy Shevchenko
2021-11-30 15:32 ` [PATCH 6/7] device property: Use fwnode_graph_for_each_endpoint() macro Sakari Ailus
2021-11-30 15:32 ` [PATCH 7/7] device property: Drop fwnode_graph_get_remote_node() Sakari Ailus
2021-11-30 16:05   ` Andy Shevchenko
2021-11-30 20:40     ` Sakari Ailus
2021-11-30 16:07 ` [PATCH 1/7] device property: Fix fwnode_graph_devcon_match() fwnode leak Andy Shevchenko
2021-11-30 20:21   ` Sakari Ailus
2021-12-01 13:19   ` Sakari Ailus

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=YaZKBpJi2C/R/6VO@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=/tmp/small/0000-cover-letter.patch@punajuuri.localdomain \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sakari.ailus@linux.intel.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