From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: [for-next][PATCH 4/6] kernel: trace: Mundane typo fixes in the file trace_events_filter.c
Date: Fri, 26 Mar 2021 17:28:52 -0400 [thread overview]
Message-ID: <20210326212926.145216505@goodmis.org> (raw)
In-Reply-To: 20210326212848.385566448@goodmis.org
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
s/callin/calling/
Link: https://lkml.kernel.org/r/20210317095401.1854544-1-unixbhaskar@gmail.com
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
[ Other fixes already done by Ingo Molnar ]
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.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
next prev parent reply other threads:[~2021-03-26 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 21:28 [for-next][PATCH 0/6] tracing: More updates for 5.13 Steven Rostedt
2021-03-26 21:28 ` [for-next][PATCH 1/6] scripts/recordmcount.pl: Make indent spacing consistent Steven Rostedt
2021-03-26 21:28 ` [for-next][PATCH 2/6] scripts/recordmcount.pl: Make vim and emacs indent the same Steven Rostedt
2021-03-26 21:28 ` [for-next][PATCH 3/6] tracing: Fix various typos in comments Steven Rostedt
2021-03-26 21:28 ` Steven Rostedt [this message]
2021-03-26 21:28 ` [for-next][PATCH 5/6] tracing: A minor cleanup for create_system_filter() Steven Rostedt
2021-03-26 21:28 ` [for-next][PATCH 6/6] tracing: Update create_system_filter() kernel-doc comment Steven Rostedt
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=20210326212926.145216505@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.com \
/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