[PATCH 1/2] smatch: fix several typos

[Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>]

Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
---
 README-smatch                  |    2 +-
 check_propagate.c              |    2 +-
 smatch.c                       |    2 +-
 smatch_db.c                    |    2 +-
 smatch_extra.h                 |    2 +-
 smatch_scripts/call_tree.pl    |    2 +-
 smatch_scripts/trace_params.pl |    2 +-
 7 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/README-smatch b/README-smatch
index dd65f12..5618387 100644
--- a/README-smatch
+++ b/README-smatch
@@ -44,7 +44,7 @@ instead of smatch.  So when I am writing kernel patches in vim I do:
 	***Debugging Hints***
 
 Sometimes it is not obvious why smatch is printing an error.  The --debug
-option is usefull here.  It prints a message on each state change.
+option is useful here.  It prints a message on each state change.
 
 Also if smatch crashes, use:  kchecker --valgrind drivers/whatever/file.c and
 send me the stack dump.
diff --git a/check_propagate.c b/check_propagate.c
index 949c8c3..c3cf918 100644
--- a/check_propagate.c
+++ b/check_propagate.c
@@ -8,7 +8,7 @@
  */
 
 /*
- * People should just return the error codes they recieved 
+ * People should just return the error codes they received
  * instead of making up there own dumb error codes all the time.
  */
 
diff --git a/smatch.c b/smatch.c
index 032559d..e3f19ad 100644
--- a/smatch.c
+++ b/smatch.c
@@ -76,7 +76,7 @@ static void help(void)
 	printf("--known-conditions:  don't branch for known conditions.\n");
 	printf("--two-passes:  use a two pass system for each function.\n");
 	printf("--file-output:  instead of printing stdout, print to \"file.c.smatch_out\".\n");
-	printf("--help:  print this helpfull message.\n");
+	printf("--help:  print this helpful message.\n");
 	exit(1);
 }
 
diff --git a/smatch_db.c b/smatch_db.c
index 8a72b00..98d3595 100644
--- a/smatch_db.c
+++ b/smatch_db.c
@@ -127,7 +127,7 @@ static void match_call_hack(struct expression *expr)
 
 	/*
 	 * we just want to record something in the database so that if we have
-	 * two calls like:  frob(4); frob(some_unkown); then on the recieving
+	 * two calls like:  frob(4); frob(some_unkown); then on the receiving
 	 * side we know that sometimes frob is called with unknown parameters.
 	 */
 
diff --git a/smatch_extra.h b/smatch_extra.h
index 94adaae..308dd38 100644
--- a/smatch_extra.h
+++ b/smatch_extra.h
@@ -34,7 +34,7 @@ extern struct string_list *__ignored_macros;
 extern struct smatch_state estate_undefined;
 void alloc_estate_undefined(void);
 
-/* these are implimented in smatch_ranges.c */
+/* these are implemented in smatch_ranges.c */
 int is_whole_range_rl(struct range_list *rl);
 long long rl_min(struct range_list *rl);
 long long rl_max(struct range_list *rl);
diff --git a/smatch_scripts/call_tree.pl b/smatch_scripts/call_tree.pl
index bb81f3f..745a537 100755
--- a/smatch_scripts/call_tree.pl
+++ b/smatch_scripts/call_tree.pl
@@ -2,7 +2,7 @@
 
 # This script is supposed to help use the param_mapper output.
 # Give it a function and parameter and it lists the functions
-# and parameters which are basically equivelent.
+# and parameters which are basically equivalent.
 
 use strict;
 
diff --git a/smatch_scripts/trace_params.pl b/smatch_scripts/trace_params.pl
index 4a720a1..4276c70 100755
--- a/smatch_scripts/trace_params.pl
+++ b/smatch_scripts/trace_params.pl
@@ -2,7 +2,7 @@
 
 # This script is supposed to help use the param_mapper output.
 # Give it a function and parameter and it lists the functions
-# and parameters which are basically equivelent.
+# and parameters which are basically equivalent.
 
 use strict;
 
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe smatch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html