[PATCH] Documentation/driver-api: Fix typo error in cxl

[PATCH] Documentation/driver-api: Fix typo error in cxl

[rakuram]

Fixed the following typo errors

intersparsed ==> interspersed
in Documentation/driver-api/cxl/platform/bios-and-efi.rst

ndoe ==> node
in Documentation/driver-api/cxl/allocation/page-allocator.rst

Signed-off-by: rakuram <rakuram.e96@gmail.com>
---
 Documentation/driver-api/cxl/allocation/page-allocator.rst | 2 +-
 Documentation/driver-api/cxl/platform/bios-and-efi.rst     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/driver-api/cxl/allocation/page-allocator.rst b/Documentation/driver-api/cxl/allocation/page-allocator.rst
index 7b8fe1b8d5bb..4ac3368c3947 100644
--- a/Documentation/driver-api/cxl/allocation/page-allocator.rst
+++ b/Documentation/driver-api/cxl/allocation/page-allocator.rst
@@ -62,7 +62,7 @@ Because the local node does not have :code:`ZONE_MOVABLE`, the CXL node is
 functionally unreachable for direct allocation.  As a result, the only way
 for CXL capacity to be used is via `demotion` in the reclaim path.
 
-This configuration also means that if the DRAM ndoe has :code:`ZONE_MOVABLE`
+This configuration also means that if the DRAM node has :code:`ZONE_MOVABLE`
 capacity - when that capacity is depleted, the page allocator will actually
 prefer CXL :code:`ZONE_MOVABLE` pages over DRAM :code:`ZONE_NORMAL` pages.
 
diff --git a/Documentation/driver-api/cxl/platform/bios-and-efi.rst b/Documentation/driver-api/cxl/platform/bios-and-efi.rst
index 645322632cc9..a9aa0ccd92af 100644
--- a/Documentation/driver-api/cxl/platform/bios-and-efi.rst
+++ b/Documentation/driver-api/cxl/platform/bios-and-efi.rst
@@ -202,7 +202,7 @@ future and such a configuration should be avoided.
 
 Memory Holes
 ------------
-If your platform includes memory holes intersparsed between your CXL memory, it
+If your platform includes memory holes interspersed between your CXL memory, it
 is recommended to utilize multiple decoders to cover these regions of memory,
 rather than try to program the decoders to accept the entire range and expect
 Linux to manage the overlap.
-- 
2.43.0

Re: [PATCH] Documentation/driver-api: Fix typo error in cxl

[Randy Dunlap]

On 8/16/25 11:30 AM, rakuram wrote:
> Fixed the following typo errors
> 
> intersparsed ==> interspersed
> in Documentation/driver-api/cxl/platform/bios-and-efi.rst
> 
> ndoe ==> node
> in Documentation/driver-api/cxl/allocation/page-allocator.rst
> 
> Signed-off-by: rakuram <rakuram.e96@gmail.com>

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

Thanks.

> ---
>  Documentation/driver-api/cxl/allocation/page-allocator.rst | 2 +-
>  Documentation/driver-api/cxl/platform/bios-and-efi.rst     | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/driver-api/cxl/allocation/page-allocator.rst b/Documentation/driver-api/cxl/allocation/page-allocator.rst
> index 7b8fe1b8d5bb..4ac3368c3947 100644
> --- a/Documentation/driver-api/cxl/allocation/page-allocator.rst
> +++ b/Documentation/driver-api/cxl/allocation/page-allocator.rst
> @@ -62,7 +62,7 @@ Because the local node does not have :code:`ZONE_MOVABLE`, the CXL node is
>  functionally unreachable for direct allocation.  As a result, the only way
>  for CXL capacity to be used is via `demotion` in the reclaim path.
>  
> -This configuration also means that if the DRAM ndoe has :code:`ZONE_MOVABLE`
> +This configuration also means that if the DRAM node has :code:`ZONE_MOVABLE`
>  capacity - when that capacity is depleted, the page allocator will actually
>  prefer CXL :code:`ZONE_MOVABLE` pages over DRAM :code:`ZONE_NORMAL` pages.
>  
> diff --git a/Documentation/driver-api/cxl/platform/bios-and-efi.rst b/Documentation/driver-api/cxl/platform/bios-and-efi.rst
> index 645322632cc9..a9aa0ccd92af 100644
> --- a/Documentation/driver-api/cxl/platform/bios-and-efi.rst
> +++ b/Documentation/driver-api/cxl/platform/bios-and-efi.rst
> @@ -202,7 +202,7 @@ future and such a configuration should be avoided.
>  
>  Memory Holes
>  ------------
> -If your platform includes memory holes intersparsed between your CXL memory, it
> +If your platform includes memory holes interspersed between your CXL memory, it
>  is recommended to utilize multiple decoders to cover these regions of memory,
>  rather than try to program the decoders to accept the entire range and expect
>  Linux to manage the overlap.

-- 
~Randy

Re: [PATCH] Documentation/driver-api: Fix typo error in cxl

[Gregory Price]

On Sun, Aug 17, 2025 at 12:00:33AM +0530, rakuram wrote:
> diff --git a/Documentation/driver-api/cxl/allocation/page-allocator.rst b/Documentation/driver-api/cxl/allocation/page-allocator.rst
> index 7b8fe1b8d5bb..4ac3368c3947 100644
> --- a/Documentation/driver-api/cxl/allocation/page-allocator.rst
> +++ b/Documentation/driver-api/cxl/allocation/page-allocator.rst
> @@ -62,7 +62,7 @@ Because the local node does not have :code:`ZONE_MOVABLE`, the CXL node is
>  functionally unreachable for direct allocation.  As a result, the only way
>  for CXL capacity to be used is via `demotion` in the reclaim path.
>  
> -This configuration also means that if the DRAM ndoe has :code:`ZONE_MOVABLE`
> +This configuration also means that if the DRAM node has :code:`ZONE_MOVABLE`
>  capacity - when that capacity is depleted, the page allocator will actually
>  prefer CXL :code:`ZONE_MOVABLE` pages over DRAM :code:`ZONE_NORMAL` pages.
>

I have since discovered that this area of documentation is incorrect,
and this behavior is the result of bad reclaim logic.  I will rewrite
this area shortly.


Just drop the page-allocator.rst chunk please.

Reviewed-by: Gregory Price <gourry@gourry.net>

~Gregory

Re: [PATCH] Documentation/driver-api: Fix typo error in cxl

[rakuram]

Ok, Gregory. 

I will send v2 without page-allocator changes as suggested. 

[PATCH] Documentation/driver-api: Fix typo error in cxl

[Moktar SELLAMI]

Fixed Typo in the driver-api/cxl/devices/devices.rst

functionalty -> functionality

Signed-off-by: Moktar SELLAMI <smokthar925@gmail.com>
---
 Documentation/driver-api/cxl/devices/device-types.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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).
 
-- 
2.34.1

Re: [PATCH] Documentation/driver-api: Fix typo error in cxl

[Jonathan Cameron]

On Tue, 19 Aug 2025 09:41:16 +0100
Moktar SELLAMI <smokthar925@gmail.com> wrote:

> Fixed Typo in the driver-api/cxl/devices/devices.rst
> 
> functionalty -> functionality
> 
> Signed-off-by: Moktar SELLAMI <smokthar925@gmail.com>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>

> ---
>  Documentation/driver-api/cxl/devices/device-types.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> 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).
>  

Re: [PATCH] Documentation/driver-api: Fix typo error in cxl

[Randy Dunlap]

On 8/19/25 1:41 AM, Moktar SELLAMI wrote:
> Fixed Typo in the driver-api/cxl/devices/devices.rst
> 
> functionalty -> functionality
> 
> Signed-off-by: Moktar SELLAMI <smokthar925@gmail.com>

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

Thanks.

> ---
>  Documentation/driver-api/cxl/devices/device-types.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> 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).
>  

-- 
~Randy

Re: [PATCH] Documentation/driver-api: Fix typo error in cxl

[Jonathan Corbet]

Moktar SELLAMI <smokthar925@gmail.com> writes:

> Fixed Typo in the driver-api/cxl/devices/devices.rst
>
> functionalty -> functionality
>
> Signed-off-by: Moktar SELLAMI <smokthar925@gmail.com>
> ---
>  Documentation/driver-api/cxl/devices/device-types.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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).

This one was fixed a while back, so this patch is not needed.  It is
always a good idea to check linux-next when considering changes of this
type.

Thanks,

jon

Re: [PATCH] Documentation/driver-api: Fix typo error in cxl

[Moktar sellami]

On 8/29/25 23:35, Jonathan Corbet wrote:
> Moktar SELLAMI <smokthar925@gmail.com> writes:
>
>> Fixed Typo in the driver-api/cxl/devices/devices.rst
>>
>> functionalty -> functionality
>>
>> Signed-off-by: Moktar SELLAMI <smokthar925@gmail.com>
>> ---
>>   Documentation/driver-api/cxl/devices/device-types.rst | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> 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).
> This one was fixed a while back, so this patch is not needed.  It is
> always a good idea to check linux-next when considering changes of this
> type.
>
> Thanks,
>
> jon

Thank you for the clarification and for pointing me to linux-next. i 
will try to come up with an other patch thank u.

Moktar