From: "Kurt Borja" <kuurtb@gmail.com>
To: "Soham Metha" <sohammetha01@gmail.com>, <linux-doc@vger.kernel.org>
Cc: <linux-kernel-mentees@lists.linuxfoundation.org>,
<skhan@linuxfoundation.org>, "Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH v2 5/9] docs: alienware-wmi: fixed spelling mistake in admin guide
Date: Tue, 12 Aug 2025 16:21:20 -0500 [thread overview]
Message-ID: <DC0RIMIRP717.345GQONQFW4HI@gmail.com> (raw)
In-Reply-To: <20250812204952.73136-3-sohammetha01@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Hi Soham,
On Tue Aug 12, 2025 at 3:49 PM -05, Soham Metha wrote:
> found/fixed the following typo
>
> - aproximate -> approximate
Thanks!
>
> in `Documentation/admin-guide/laptops/alienware-wmi.rst`
>
> Signed-off-by: Soham Metha <sohammetha01@gmail.com>
Please, Cc this to the appropriate subsystem and maintainers. You can
check MAINTAINERS or use ./scripts/get_maintainer.pl.
After that is addressed:
Reviewed-by: Kurt Borja <kuurtb@gmail.com>
> ---
> Documentation/admin-guide/laptops/alienware-wmi.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/laptops/alienware-wmi.rst b/Documentation/admin-guide/laptops/alienware-wmi.rst
> index 27a32a8057da..e532c60db8e2 100644
> --- a/Documentation/admin-guide/laptops/alienware-wmi.rst
> +++ b/Documentation/admin-guide/laptops/alienware-wmi.rst
> @@ -105,7 +105,7 @@ information.
>
> Manual fan control on the other hand, is not exposed directly by the AWCC
> interface. Instead it let's us control a fan `boost` value. This `boost` value
> -has the following aproximate behavior over the fan pwm:
> +has the following approximate behavior over the fan pwm:
>
> ::
>
--
~ Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-12 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 20:15 [PATCH v2 0/9] docs: fix spelling mistakes across multiple directories Soham Metha
2025-08-12 20:15 ` [PATCH v2 1/9] docs: f2fs: fixed spelling mistakes in documentation Soham Metha
2025-08-13 3:13 ` Chao Yu
2025-08-12 20:49 ` [PATCH v2 3/9] docs: cgroup: " Soham Metha
2025-08-12 20:49 ` [PATCH v2 4/9] docs: device-mapper: " Soham Metha
2025-08-14 13:58 ` Mikulas Patocka
2025-08-12 20:49 ` [PATCH v2 5/9] docs: alienware-wmi: fixed spelling mistake in admin guide Soham Metha
2025-08-12 21:21 ` Kurt Borja [this message]
[not found] ` <dea5d89e-d918-4d80-a205-38ca7c166cc3@gmail.com>
[not found] ` <DC10RH2NVBR9.3QC7LKK4O4CW1@gmail.com>
2025-08-13 12:09 ` Soham Metha
2025-08-12 20:49 ` [PATCH v2 6/9] docs: damon: fixed spelling mistakes in documentation Soham Metha
2025-08-12 21:12 ` SeongJae Park
2025-08-12 20:49 ` [PATCH v2 7/9] docs: loongarch: fixed spelling mistake " Soham Metha
2025-08-12 20:52 ` [PATCH v2 3/9] docs: cgroup: fixed spelling mistakes " Tejun Heo
2025-08-12 21:01 ` [PATCH v2 8/9] docs: admin-guide: tainted-kernels: fixed spelling mistake " Soham Metha
2025-08-12 21:04 ` [PATCH v2 9/9] docs: symbol-namespaces: " Soham Metha
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=DC0RIMIRP717.345GQONQFW4HI@gmail.com \
--to=kuurtb@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=skhan@linuxfoundation.org \
--cc=sohammetha01@gmail.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