From: "Emilio G. Cota" <cota@braap.org>
To: ccan@lists.ozlabs.org
Subject: [PATCH] list: trivial: fix typos in list_for_each_off's documentation
Date: Thu, 29 Sep 2016 17:54:13 -0400 [thread overview]
Message-ID: <1475186053-6436-1-git-send-email-cota@braap.org> (raw)
Signed-off-by: Emilio G. Cota <cota@braap.org>
---
ccan/list/list.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/ccan/list/list.h b/ccan/list/list.h
index a4c21f1..a6b0038 100644
--- a/ccan/list/list.h
+++ b/ccan/list/list.h
@@ -716,12 +716,12 @@ static inline void list_prepend_list_(struct list_head *to,
* 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
+ * properly filled `struct list_node' which in turn contains pointers to
+ * 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
--
2.5.0
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
next reply other threads:[~2016-09-29 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 21:54 Emilio G. Cota [this message]
2016-09-29 23:42 ` [PATCH] list: trivial: fix typos in list_for_each_off's documentation David Gibson
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=1475186053-6436-1-git-send-email-cota@braap.org \
--to=cota@braap.org \
--cc=ccan@lists.ozlabs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).