From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH] doc: reformulate an item in the TODO
Date: Tue, 16 Jun 2020 23:04:13 +0200 [thread overview]
Message-ID: <20200616210413.77884-1-luc.vanoostenryck@gmail.com> (raw)
One of the item wasn't even grammatical. Reformulate it.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
Documentation/TODO.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/TODO.md b/Documentation/TODO.md
index 64c1523cdbd0..e2043e481f99 100644
--- a/Documentation/TODO.md
+++ b/Documentation/TODO.md
@@ -84,8 +84,8 @@ Longer term/to investigate
"warning: Variable length array is used. (-Wno-vla)"
-* ptrlists must have elements be removed while being iterated but this
- is hard to insure it is not done.
+* ptrlists must not have elements removed while being iterated;
+ this should somehow be enforced.
* having 'struct symbol' used to represent symbols *and* types is
quite handy but it also creates lots of problems and complications
* Possible mixup of symbol for a function designator being not a pointer?
--
2.27.0
reply other threads:[~2020-06-16 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200616210413.77884-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).