linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Linux-Sparse <linux-sparse@vger.kernel.org>,
	Christopher Li <sparse@chrisli.org>
Cc: Josh Triplett <josh@joshtriplett.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH] Documentation: editing fixes in test-suite
Date: Sun, 21 Jan 2018 21:38:39 -0800	[thread overview]
Message-ID: <5bf3731a-c3be-e94e-2aaf-4c443e6ed870@infradead.org> (raw)

From: Randy Dunlap <rdunlap@infradead.org>

Fix typos, grammar, punctuation, and spelling in Documentation/test-suite.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>
---
 Documentation/test-suite |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

--- sprs-2018-0119.orig/Documentation/test-suite
+++ sprs-2018-0119/Documentation/test-suite
@@ -35,7 +35,7 @@ check-output-start / check-output-end (o
 
 check-output-ignore / check-error-ignore (optional)
 	Don't check the expected output (stdout or stderr) of check-command
-	(usefull when this output is not comparable or if you're only interested
+	(useful when this output is not comparable or if you're only interested
 	in the exit value).
 	By default this check is done.
 
@@ -54,8 +54,8 @@ check-output-excludes: <pattern> (option
 	must contains none of the patterns.
 
 check-output-pattern-<nbr>-times: <pattern> (optional)
-	Similar than the contains/excludes her above, but with full control
-	of the number of times the pattern should occurs in the output.
+	Similar to the contains/excludes above, but with full control
+	of the number of times the pattern should occur in the output.
 
 	Using test-suite
 	~~~~~~~~~~~~~~~~
@@ -84,7 +84,7 @@ cmd:
 	"sparse $file".
 
 The output of the test-suite format command can be redirected into the
-test case to create a test-suite formated file.
+test case to create a test-suite formatted file.
 
 $ ./test-suite format bad-assignment.c Assignment >> bad-assignment.c
 $ cat !$



             reply	other threads:[~2018-01-22  5:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22  5:38 Randy Dunlap [this message]
2018-01-22  5:48 ` [PATCH] Documentation: editing fixes in test-suite Luc Van Oostenryck
2018-01-22 15:31 ` Josh Triplett
2018-01-23 10:59 ` Christopher Li

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=5bf3731a-c3be-e94e-2aaf-4c443e6ed870@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=sparse@chrisli.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).