From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: linux-nvdimm@lists.01.org
Subject: [ndctl PATCH 2/2] ndctl: fix some spelling mistakes
Date: Mon, 9 Apr 2018 14:09:20 -0600 [thread overview]
Message-ID: <20180409200920.20177-2-ross.zwisler@linux.intel.com> (raw)
In-Reply-To: <20180409200920.20177-1-ross.zwisler@linux.intel.com>
Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
---
Documentation/ndctl/ndctl-create-namespace.txt | 2 +-
ccan/list/list.h | 12 ++++++------
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/ndctl/ndctl-create-namespace.txt b/Documentation/ndctl/ndctl-create-namespace.txt
index 14c5409..29c55f5 100644
--- a/Documentation/ndctl/ndctl-create-namespace.txt
+++ b/Documentation/ndctl/ndctl-create-namespace.txt
@@ -42,7 +42,7 @@ OPTIONS
-m::
--mode=::
- "raw": expose the namespace capacity directly with
- limitations. Neither a raw pmem namepace nor raw blk
+ limitations. Neither a raw pmem namespace nor raw blk
namespace support sector atomicity by default (see "sector"
mode below). A raw pmem namespace may have limited to no dax
support depending the kernel. In other words operations like
diff --git a/ccan/list/list.h b/ccan/list/list.h
index 4d1d34e..b4c2d75 100644
--- a/ccan/list/list.h
+++ b/ccan/list/list.h
@@ -540,20 +540,20 @@ static inline void list_prepend_list_(struct list_head *to,
/**
* list_for_each_off - iterate through a list of memory regions.
* @h: the list_head
- * @i: the pointer to a memory region wich contains list node data.
+ * @i: the pointer to a memory region which contains list node data.
* @off: offset(relative to @i) at which list node data resides.
*
* This is a low-level wrapper to iterate @i over the entire list, used to
- * implement all oher, more high-level, for-each constructs. It's a for loop,
+ * implement all other, more high-level, for-each constructs. It's a for loop,
* so you can break and continue as normal.
*
* WARNING! Being the low-level macro that it is, this wrapper doesn't know
- * nor care about the type of @i. The only assumtion made is that @i points
+ * nor care about the type of @i. The only assumption made is that @i points
* to a chunk of memory that at some @offset, relative to @i, contains a
* properly filled `struct node_list' which in turn contains pointers to
- * memory chunks and it's turtles all the way down. Whith all that in mind
+ * memory chunks and it's turtles all the way down. With all that in mind
* remember that given the wrong pointer/offset couple this macro will
- * happilly churn all you memory untill SEGFAULT stops it, in other words
+ * happily churn all you memory until SEGFAULT stops it, in other words
* caveat emptor.
*
* It is worth mentioning that one of legitimate use-cases for that wrapper
@@ -577,7 +577,7 @@ static inline void list_prepend_list_(struct list_head *to,
* list_for_each_safe_off - iterate through a list of memory regions, maybe
* during deletion
* @h: the list_head
- * @i: the pointer to a memory region wich contains list node data.
+ * @i: the pointer to a memory region which contains list node data.
* @nxt: the structure containing the list_node
* @off: offset(relative to @i) at which list node data resides.
*
--
2.14.3
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-04-09 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 20:09 [ndctl PATCH 1/2] ndctl: s/memory/fsdax/ in some user visible places Ross Zwisler
2018-04-09 20:09 ` Ross Zwisler [this message]
2018-04-09 20:34 ` [ndctl PATCH 2/2] ndctl: fix some spelling mistakes Dan Williams
2018-04-09 22:10 ` [ndctl PATCH 1/2] ndctl: s/memory/fsdax/ in some user visible places Dan Williams
2018-04-09 23:07 ` Ross Zwisler
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=20180409200920.20177-2-ross.zwisler@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=linux-nvdimm@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.