From: Armin Wolf <W_Armin@gmx.de>
To: Anaswara T Rajan <anaswaratrajan@gmail.com>
Cc: corbet@lwn.net, platform-driver-x86@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] platform/x86: dell-ddv: Fix typo in documentation
Date: Sat, 5 Oct 2024 17:12:22 +0200 [thread overview]
Message-ID: <f0d2200d-536b-4572-b7ef-63be26dd03a5@gmx.de> (raw)
In-Reply-To: <20241005070056.16326-1-anaswaratrajan@gmail.com>
Am 05.10.24 um 09:00 schrieb Anaswara T Rajan:
> Fix typo in word 'diagnostics' in documentation.
>
> Signed-off-by: Anaswara T Rajan <anaswaratrajan@gmail.com>
Thanks, for the whole patch:
Reviewed-by: Armin Wolf <W_Armin@gmx.de>
> ---
> Changes in v2:
> - Make the commit title and description more clearer.
>
> Changes in v3:
> - Add missing full stop to commit description.
>
> Documentation/wmi/devices/dell-wmi-ddv.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/wmi/devices/dell-wmi-ddv.rst b/Documentation/wmi/devices/dell-wmi-ddv.rst
> index 2fcdfcf03327..e0c20af30948 100644
> --- a/Documentation/wmi/devices/dell-wmi-ddv.rst
> +++ b/Documentation/wmi/devices/dell-wmi-ddv.rst
> @@ -8,7 +8,7 @@ Introduction
> ============
>
> Many Dell notebooks made after ~2020 support a WMI-based interface for
> -retrieving various system data like battery temperature, ePPID, diagostic data
> +retrieving various system data like battery temperature, ePPID, diagnostic data
> and fan/thermal sensor data.
>
> This interface is likely used by the `Dell Data Vault` software on Windows,
> @@ -277,7 +277,7 @@ Reverse-Engineering the DDV WMI interface
> 4. Try to deduce the meaning of a certain WMI method by comparing the control
> flow with other ACPI methods (_BIX or _BIF for battery related methods
> for example).
> -5. Use the built-in UEFI diagostics to view sensor types/values for fan/thermal
> +5. Use the built-in UEFI diagnostics to view sensor types/values for fan/thermal
> related methods (sometimes overwriting static ACPI data fields can be used
> to test different sensor type values, since on some machines this data is
> not reinitialized upon a warm reset).
next prev parent reply other threads:[~2024-10-05 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 7:00 Anaswara T Rajan
2024-10-05 15:12 ` Armin Wolf [this message]
2024-10-05 21:44 ` Armin Wolf
2024-10-06 10:48 ` Hans de Goede
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=f0d2200d-536b-4572-b7ef-63be26dd03a5@gmx.de \
--to=w_armin@gmx.de \
--cc=anaswaratrajan@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®