[PATCH v2] Documentation: Fix driver-api typos

[PATCH v2] Documentation: Fix driver-api typos

[Ranganath V N]

Corrected a few spelling mistakes

v2:
* corrected as per suggestions.
* improved the phrasing.

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@gmail.com>
---
 .../driver-api/cxl/devices/device-types.rst        |  2 +-
 .../example-configurations/one-dev-per-hb.rst      |  2 +-
 .../thermal/exynos_thermal_emulation.rst           | 14 +++++++-------
 3 files changed, 9 insertions(+), 9 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..c679502f01c7 100644
--- a/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
+++ b/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
@@ -28,13 +28,13 @@ changed into it.
 delay of changing temperature. However, this node only uses same delay
 of real sensing time, 938us.)
 
-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
-repeatedly. That's why this node gives users the right to change
-termerpature only. Just one interface makes it more simply to use.
+Exynos emulation mode requires that value changes and enabling are performed
+synchronously. This means that when you want to update any value, such as the
+delay or the next temperature, you must enable emulation mode at the same
+time (or keep the mode enabled). If you do not, the value will fail to update
+and the last successful value will continue to be used. For this reason,
+this node only allows users to change the temperature. Providing a single
+interface makes it simpler to use.
 
 Disabling emulation mode only requires writing value 0 to sysfs node.
 
-- 
2.43.0

Re: [PATCH v2] Documentation: Fix driver-api typos

[Randy Dunlap]

On 8/14/25 11:43 AM, Ranganath V N wrote:
> Corrected a few spelling mistakes
> 
> v2:
> * corrected as per suggestions.
> * improved the phrasing.
> 
> 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@gmail.com>

Looks good. Thanks.
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  .../driver-api/cxl/devices/device-types.rst        |  2 +-
>  .../example-configurations/one-dev-per-hb.rst      |  2 +-
>  .../thermal/exynos_thermal_emulation.rst           | 14 +++++++-------
>  3 files changed, 9 insertions(+), 9 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..c679502f01c7 100644
> --- a/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> +++ b/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> @@ -28,13 +28,13 @@ changed into it.
>  delay of changing temperature. However, this node only uses same delay
>  of real sensing time, 938us.)
>  
> -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
> -repeatedly. That's why this node gives users the right to change
> -termerpature only. Just one interface makes it more simply to use.
> +Exynos emulation mode requires that value changes and enabling are performed
> +synchronously. This means that when you want to update any value, such as the
> +delay or the next temperature, you must enable emulation mode at the same
> +time (or keep the mode enabled). If you do not, the value will fail to update
> +and the last successful value will continue to be used. For this reason,
> +this node only allows users to change the temperature. Providing a single
> +interface makes it simpler to use.
>  
>  Disabling emulation mode only requires writing value 0 to sysfs node.
>  

-- 
~Randy

Re: [PATCH v2] Documentation: Fix driver-api typos

[Jonathan Corbet]

Ranganath V N <vnranganath.20@gmail.com> writes:

> Corrected a few spelling mistakes
>
> v2:
> * corrected as per suggestions.
> * improved the phrasing.

For future reference, this information should go below the "---" line so
that the person applying the patch does not have to edit it out.  I can
take care of it this time, no need to resend.

Thanks,

jon