From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: Gregory Price <gourry@gourry.net>
Cc: dave@stgolabs.net, jonathan.cameron@huawei.com,
dave.jiang@intel.com, alison.schofield@intel.com,
vishal.l.verma@intel.com, ira.weiny@intel.com,
dan.j.williams@intel.com, corbet@lwn.net,
linux-cxl@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, darren.kenny@oracle.com
Subject: Re: [PATCH] Documentation: cxl: fix typos and improve clarity in memory-devices.rst
Date: Mon, 2 Jun 2025 19:02:00 +0530 [thread overview]
Message-ID: <5f50fd5d-a3e0-4f71-b530-b8dfe6fa22c9@oracle.com> (raw)
In-Reply-To: <aDzipGmldaeje43H@gourry-fedora-PF4VCD3F>
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@oracle.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@gourry.net>
Thanks,
Alok
next prev parent reply other threads:[~2025-06-02 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 7:51 Alok Tiwari
2025-05-31 16:57 ` Randy Dunlap
2025-06-01 23:30 ` Gregory Price
2025-06-02 13:32 ` ALOK TIWARI [this message]
2025-06-09 10:58 ` Jonathan Cameron
2025-06-09 12:59 ` ALOK TIWARI
2025-06-09 16:36 ` Dave Jiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f50fd5d-a3e0-4f71-b530-b8dfe6fa22c9@oracle.com \
--to=alok.a.tiwari@oracle.com \
--cc=alison.schofield@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=darren.kenny@oracle.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®