From: "Rafael J. Wysocki" <rafael@kernel.org>
To: John Watts <contact@jookia.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: firmware-guide: ACPI: Fix namespace typo
Date: Fri, 26 Apr 2024 18:59:41 +0200 [thread overview]
Message-ID: <CAJZ5v0iEcPO0GrjudTWOSn6UVoV7UbjCi3fNpAa3A1+8UbCfcw@mail.gmail.com> (raw)
In-Reply-To: <20240424-acpidocfix-v1-1-078658a3c456@jookia.org>
On Wed, Apr 24, 2024 at 12:17 AM John Watts <contact@jookia.org> wrote:
>
> The ACPI namespace has always started with LNXSYSTM, not LNXSYSTEM.
> Fix the documentation accordingly.
>
> Signed-off-by: John Watts <contact@jookia.org>
> ---
> This isn't a major issue, it just is incorrect and requires people
> following the documentation to look for a similar directory.
> ---
> Documentation/firmware-guide/acpi/namespace.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/firmware-guide/acpi/namespace.rst b/Documentation/firmware-guide/acpi/namespace.rst
> index 4ef963679a3d..5021843b526b 100644
> --- a/Documentation/firmware-guide/acpi/namespace.rst
> +++ b/Documentation/firmware-guide/acpi/namespace.rst
> @@ -15,7 +15,7 @@ ACPI Device Tree - Representation of ACPI Namespace
> Abstract
> ========
> The Linux ACPI subsystem converts ACPI namespace objects into a Linux
> -device tree under the /sys/devices/LNXSYSTEM:00 and updates it upon
> +device tree under the /sys/devices/LNXSYSTM:00 and updates it upon
> receiving ACPI hotplug notification events. For each device object
> in this hierarchy there is a corresponding symbolic link in the
> /sys/bus/acpi/devices.
> @@ -326,7 +326,7 @@ example ACPI namespace illustrated in Figure 2 with the addition of
> fixed PWR_BUTTON/SLP_BUTTON devices is shown below::
>
> +--------------+---+-----------------+
> - | LNXSYSTEM:00 | \ | acpi:LNXSYSTEM: |
> + | LNXSYSTM:00 | \ | acpi:LNXSYSTM: |
> +--------------+---+-----------------+
> |
> | +-------------+-----+----------------+
>
> ---
Applied as 6.10 material, thanks!
prev parent reply other threads:[~2024-04-26 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:16 [PATCH] Documentation: firmware-guide: ACPI: Fix namespace typo John Watts
2024-04-26 16:59 ` Rafael J. Wysocki [this message]
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=CAJZ5v0iEcPO0GrjudTWOSn6UVoV7UbjCi3fNpAa3A1+8UbCfcw@mail.gmail.com \
--to=rafael@kernel.org \
--cc=contact@jookia.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).