NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Cc: Dave Jiang <dave.jiang@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Minwoo Im <minwoo.im.dev@gmail.com>
Subject: [ndctl PATCH 1/3] cxl/list: Fix typo in cxl-list documentation
Date: Wed, 10 May 2023 00:24:25 +0900	[thread overview]
Message-ID: <20230509152427.6920-2-minwoo.im.dev@gmail.com> (raw)
In-Reply-To: <20230509152427.6920-1-minwoo.im.dev@gmail.com>

s/the returned the returned object/the returned object
s/ellided/elided
s/hierararchy/hierarchy
s/specifed/specified
s/identidier/identifier
s/scenerios/scenarios

Signed-off-by: Minwoo Im <minwoo.im.dev@gmail.com>
---
 Documentation/cxl/cxl-list.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/cxl/cxl-list.txt b/Documentation/cxl/cxl-list.txt
index c64d65d3ffbe..838de4086678 100644
--- a/Documentation/cxl/cxl-list.txt
+++ b/Documentation/cxl/cxl-list.txt
@@ -18,9 +18,9 @@ instances along with some of their major attributes.
 Options can be specified to limit the output to specific objects. When a
 single object type is specified the return json object is an array of
 just those objects, when multiple objects types are specified the
-returned the returned object may be an array of arrays with the inner
-array named for the given object type. The top-level arrays are ellided
-when the objects can nest under a higher object-type in the hierararchy.
+returned object may be an array of arrays with the inner
+array named for the given object type. The top-level arrays are elided
+when the objects can nest under a higher object-type in the hierarchy.
 The potential top-level array names and their nesting properties are:
 
 "anon memdevs":: (disabled memory devices) do not nest
@@ -34,7 +34,7 @@ The potential top-level array names and their nesting properties are:
 "endpoint decoders":: nest under endpoints, or ports (if endpoints are
    not emitted) or buses (if endpoints and ports are not emitted)
 
-Filters can by specifed as either a single identidier, a space separated
+Filters can be specified as either a single identifier, a space separated
 quoted string, or a comma separated list. When multiple filter
 identifiers are specified within a filter string, like "-m
 mem0,mem1,mem2", they are combined as an 'OR' filter.  When multiple
@@ -263,7 +263,7 @@ OPTIONS
 --buses::
 	Include 'bus' / CXL root object(s) in the listing. Typically, on ACPI
 	systems the bus object is a singleton associated with the ACPI0017
-	device, but there are test scenerios where there may be multiple CXL
+	device, but there are test scenarios where there may be multiple CXL
 	memory hierarchies.
 ----
 # cxl list -B
-- 
2.34.1


  reply	other threads:[~2023-05-09 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 15:24 [ndctl PATCH 0/3] cxl: clean up and fix typos Minwoo Im
2023-05-09 15:24 ` Minwoo Im [this message]
2023-05-09 17:31   ` [ndctl PATCH 1/3] cxl/list: Fix typo in cxl-list documentation Dave Jiang
2023-05-09 15:24 ` [ndctl PATCH 2/3] cxl: region: remove redundant func name from error Minwoo Im
2023-05-09 17:32   ` Dave Jiang
2023-05-09 15:24 ` [ndctl PATCH 3/3] cxl: fix changed function name in a comment Minwoo Im
2023-05-09 17:33   ` 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=20230509152427.6920-2-minwoo.im.dev@gmail.com \
    --to=minwoo.im.dev@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --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