[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210326212926.145216505@goodmis.org>
Date: Fri, 26 Mar 2021 17:28:52 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Randy Dunlap <rdunlap@...radead.org>,
Bhaskar Chowdhury <unixbhaskar@...il.com>
Subject: [for-next][PATCH 4/6] kernel: trace: Mundane typo fixes in the file trace_events_filter.c
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
s/callin/calling/
Link: https://lkml.kernel.org/r/20210317095401.1854544-1-unixbhaskar@gmail.com
Acked-by: Randy Dunlap <rdunlap@...radead.org>
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
[ Other fixes already done by Ingo Molnar ]
Signed-off-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
---
kernel/trace/trace_events_filter.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
index 9730acf3c03e..49de3e21e9bc 100644
--- a/kernel/trace/trace_events_filter.c
+++ b/kernel/trace/trace_events_filter.c
@@ -256,7 +256,7 @@ enum {
* is "&&" we don't call update_preds(). Instead continue to "c". As the
* next token after "c" is not "&&" but the end of input, we first process the
* "&&" by calling update_preds() for the "&&" then we process the "||" by
- * callin updates_preds() with the values for processing "||".
+ * calling updates_preds() with the values for processing "||".
*
* What does that mean? What update_preds() does is to first save the "target"
* of the program entry indexed by the current program entry's "target"
--
2.30.1
Powered by blists - more mailing lists