From: Ira Weiny <ira.weiny@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: <jonathan.cameron@huawei.com>, <mst@redhat.com>,
<qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH] docs/cxl: Fix some typos
Date: Mon, 7 Nov 2022 14:16:12 -0800 [thread overview]
Message-ID: <Y2mDrMFgTZIQrraE@iweiny-desk3> (raw)
In-Reply-To: <20221107180923.27072-1-dave@stgolabs.net>
On Mon, Nov 07, 2022 at 10:09:23AM -0800, Davidlohr Bueso wrote:
> Found while reading the doc.
>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> ---
> docs/system/devices/cxl.rst | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/docs/system/devices/cxl.rst b/docs/system/devices/cxl.rst
> index abf7c1f24305..891bbd65d9d8 100644
> --- a/docs/system/devices/cxl.rst
> +++ b/docs/system/devices/cxl.rst
> @@ -83,7 +83,7 @@ CXL Fixed Memory Windows (CFMW)
> A CFMW consists of a particular range of Host Physical Address space
> which is routed to particular CXL Host Bridges. At time of generic
> software initialization it will have a particularly interleaving
> -configuration and associated Quality of Serice Throtling Group (QTG).
> +configuration and associated Quality of Service Throttling Group (QTG).
> This information is available to system software, when making
> decisions about how to configure interleave across available CXL
> memory devices. It is provide as CFMW Structures (CFMWS) in
> @@ -98,7 +98,7 @@ specification defined register interface called CXL Host Bridge
> Component Registers (CHBCR). The location of this CHBCR MMIO
> space is described to system software via a CXL Host Bridge
> Structure (CHBS) in the CEDT ACPI table. The actual interfaces
> -are identical to those used for other parts of the CXL heirarchy
> +are identical to those used for other parts of the CXL hierarchy
> as CXL Component Registers in PCI BARs.
>
> Interfaces provided include:
> @@ -111,7 +111,7 @@ Interfaces provided include:
>
> CXL Root Ports (CXL RP)
> ~~~~~~~~~~~~~~~~~~~~~~~
> -A CXL Root Port servers te same purpose as a PCIe Root Port.
> +A CXL Root Port servers the same purpose as a PCIe Root Port.
> There are a number of CXL specific Designated Vendor Specific
> Extended Capabilities (DVSEC) in PCIe Configuration Space
> and associated component register access via PCI bars.
> @@ -143,7 +143,7 @@ CXL Memory Devices - Type 3
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> CXL type 3 devices use a PCI class code and are intended to be supported
> by a generic operating system driver. They have HDM decoders
> -though in these EP devices, the decoder is reponsible not for
> +though in these EP devices, the decoder is responsible not for
> routing but for translation of the incoming host physical address (HPA)
> into a Device Physical Address (DPA).
>
> @@ -209,7 +209,7 @@ Notes:
> ranges of the system physical address map. Each CFMW has
> particular interleave setup across the CXL Host Bridges (HB)
> CFMW0 provides uninterleaved access to HB0, CFW2 provides
> - uninterleaved acess to HB1. CFW1 provides interleaved memory access
> + uninterleaved access to HB1. CFW1 provides interleaved memory access
> across HB0 and HB1.
>
> (2) **Two CXL Host Bridges**. Each of these has 2 CXL Root Ports and
> @@ -282,7 +282,7 @@ Example topology involving a switch::
> ---------------------------------------------------
> | Switch 0 USP as PCI 0d:00.0 |
> | USP has HDM decoder which direct traffic to |
> - | appropiate downstream port |
> + | appropriate downstream port |
> | Switch BUS appears as 0e |
> |x__________________________________________________|
> | | | |
> --
> 2.38.0
>
next prev parent reply other threads:[~2022-11-07 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 18:09 [PATCH] docs/cxl: Fix some typos Davidlohr Bueso
2022-11-07 22:16 ` Ira Weiny [this message]
2022-11-07 22:34 ` Alison Schofield
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=Y2mDrMFgTZIQrraE@iweiny-desk3 \
--to=ira.weiny@intel.com \
--cc=dave@stgolabs.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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