[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5f50fd5d-a3e0-4f71-b530-b8dfe6fa22c9@oracle.com>
Date: Mon, 2 Jun 2025 19:02:00 +0530
From: ALOK TIWARI <alok.a.tiwari@...cle.com>
To: Gregory Price <gourry@...rry.net>
Cc: dave@...olabs.net, jonathan.cameron@...wei.com, dave.jiang@...el.com,
alison.schofield@...el.com, vishal.l.verma@...el.com,
ira.weiny@...el.com, dan.j.williams@...el.com, corbet@....net,
linux-cxl@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, darren.kenny@...cle.com
Subject: Re: [PATCH] Documentation: cxl: fix typos and improve clarity in
memory-devices.rst
Thanks Gregory,
On 02-06-2025 05:00, Gregory Price wrote:
> On Sat, May 31, 2025 at 12:51:58AM -0700, Alok Tiwari wrote:
>> This patch corrects several typographical issues and improves phrasing
>> in memory-devices.rst:
>>
>> - Fixes duplicate word ("1 one") and adjusts phrasing for clarity.
>> - Adds missing hyphen in "on-device".
>> - Corrects "a give memory device" to "a given memory device".
>> - fix singular/plural "decoder resource" -> "decoder resources".
>> - Clarifies "spans to Host Bridges" -> "spans two Host Bridges".
>>
>> These changes improve readability and accuracy of the documentation.
>>
>> Signed-off-by: Alok Tiwari <alok.a.tiwari@...cle.com>
>> ---
>> Documentation/driver-api/cxl/memory-devices.rst | 12 ++++++------
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/driver-api/cxl/memory-devices.rst b/Documentation/driver-api/cxl/memory-devices.rst
>> index d732c42526df..e9e2952a967d 100644
>> --- a/Documentation/driver-api/cxl/memory-devices.rst
>> +++ b/Documentation/driver-api/cxl/memory-devices.rst
>> @@ -29,8 +29,8 @@ Platform firmware enumerates a menu of interleave options at the "CXL root port"
>> (Linux term for the top of the CXL decode topology). From there, PCIe topology
>> dictates which endpoints can participate in which Host Bridge decode regimes.
>> Each PCIe Switch in the path between the root and an endpoint introduces a point
>> -at which the interleave can be split. For example platform firmware may say at a
>> -given range only decodes to 1 one Host Bridge, but that Host Bridge may in turn
>> +at which the interleave can be split. For example, platform firmware may say at a
> ^^^^
> If you wouldn't mind, can you also change: "at a" - > "a"
I will replace "at a" with "a"
>
> Otherwise
>
> Reviewed-by: Gregory Price <gourry@...rry.net>
Thanks,
Alok
Powered by blists - more mailing lists