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@xxxxxxxxx> Reviewed-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> 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
