linux-kernel - Re: [PATCH] Documentation: Fix driver-api typos

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <95b81414-52d4-4e13-a894-9d59cd0e175c@infradead.org>
Date: Thu, 14 Aug 2025 08:56:34 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Ranganath V N <vnranganath.20@...il.com>, corbet@....net,
 linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, linux-cxl@...r.kernel.org,
 linux-samsung-soc@...r.kernel.org, alim.akhtar@...sung.com,
 dave@...olabs.net, rafael@...nel.org, linux-kernel-mentees@...r.kernel.org,
 skhan@...uxfoundation.org, vishal.l.verma@...el.com
Subject: Re: [PATCH] Documentation: Fix driver-api typos



On 8/14/25 4:42 AM, Ranganath V N wrote:
> Corrected a few spelling mistakes
> 
> - functionalty ==> functionality
> in Documentation/driver-api/cxl/devices/device-types.rst
> 
> - adjascent ==> adjacent
> in Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> 
> - succeessful ==> successful
> in Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> 
> Signed-off-by: Ranganath V N <vnranganath.20@...il.com>

Reviewed-by: Randy Dunlap <rdunlap@...radead.org>
Thanks.

> ---
>  Documentation/driver-api/cxl/devices/device-types.rst           | 2 +-
>  .../cxl/platform/example-configurations/one-dev-per-hb.rst      | 2 +-
>  Documentation/driver-api/thermal/exynos_thermal_emulation.rst   | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/driver-api/cxl/devices/device-types.rst b/Documentation/driver-api/cxl/devices/device-types.rst
> index 923f5d89bc04..7f69dfa4509b 100644
> --- a/Documentation/driver-api/cxl/devices/device-types.rst
> +++ b/Documentation/driver-api/cxl/devices/device-types.rst
> @@ -22,7 +22,7 @@ The basic interaction protocol, similar to PCIe configuration mechanisms.
>  Typically used for initialization, configuration, and I/O access for anything
>  other than memory (CXL.mem) or cache (CXL.cache) operations.
>  
> -The Linux CXL driver exposes access to .io functionalty via the various sysfs
> +The Linux CXL driver exposes access to .io functionality via the various sysfs
>  interfaces and /dev/cxl/ devices (which exposes direct access to device
>  mailboxes).
>  
> diff --git a/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst b/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> index aebda0eb3e17..a4c3fb51ea7d 100644
> --- a/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> +++ b/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> @@ -10,7 +10,7 @@ has a single CXL memory expander with a 4GB of memory.
>  Things to note:
>  
>  * Cross-Bridge interleave is not being used.
> -* The expanders are in two separate but adjascent memory regions.
> +* The expanders are in two separate but adjacent memory regions.
>  * This CEDT/SRAT describes one node per device
>  * The expanders have the same performance and will be in the same memory tier.
>  
> diff --git a/Documentation/driver-api/thermal/exynos_thermal_emulation.rst b/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> index c21d10838bc5..f77d27c25ce2 100644
> --- a/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> +++ b/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> @@ -32,7 +32,7 @@ Exynos emulation mode requires synchronous of value changing and
>  enabling. It means when you want to update the any value of delay or
>  next temperature, then you have to enable emulation mode at the same
>  time. (Or you have to keep the mode enabling.) If you don't, it fails to
> -change the value to updated one and just use last succeessful value
> +change the value to updated one and just use last successful value
>  repeatedly. That's why this node gives users the right to change
>  termerpature only. Just one interface makes it more simply to use.
>  

-- 
~Randy