On 3/17/21 2:54 AM, Bhaskar Chowdhury wrote:
>
> s/callin/calling/
> s/progam/program/
> s/interperate/interpret/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhas...@gmail.com>
Acked-by: Randy Dunlap <rdun...@infradead.org>
> ---
> kernel/trace/trace_events_filter.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/trace_events_filter.c
> b/kernel/trace/trace_events_filter.c
> index e91259f6a722..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"
> @@ -296,7 +296,7 @@ enum {
> * and "FALSE" the program entry after that, we are now done with the first
> * pass.
> *
> - * Making the above "a || b && c" have a progam of:
> + * Making the above "a || b && c" have a program of:
> * prog[0] = { "a", 1, 2 }
> * prog[1] = { "b", 0, 2 }
> * prog[2] = { "c", 0, 3 }
> @@ -390,7 +390,7 @@ enum {
> * F: return FALSE
> *
> * As "r = a; if (!r) goto n5;" is obviously the same as
> - * "if (!a) goto n5;" without doing anything we can interperate the
> + * "if (!a) goto n5;" without doing anything we can interpret the
> * program as:
> * n1: if (!a) goto n5;
> * n2: if (!b) goto n5;
> --
--
~Randy
