From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Roy Ben Shlomo <royb@sentinelone.com>
Cc: Roy Ben Shlomo <roy.benshlomo@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/core: fixing several typos in comments
Date: Fri, 20 Sep 2019 16:06:56 -0300 [thread overview]
Message-ID: <20190920190656.GH4865@kernel.org> (raw)
In-Reply-To: <20190920171254.31373-1-royb@sentinelone.com>
Em Fri, Sep 20, 2019 at 08:12:53PM +0300, Roy Ben Shlomo escreveu:
> From: Roy Ben Shlomo <roy.benshlomo@gmail.com>
Thanks, applied.
- Arnaldo
> Fixing typos in a few functions' documentation comments
> Signed-off-by: Roy Ben Shlomo <royb@sentinelone.com>
> ---
> kernel/events/core.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 4f08b17d6426..275eae05af20 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -2239,7 +2239,7 @@ static void __perf_event_disable(struct perf_event *event,
> *
> * If event->ctx is a cloned context, callers must make sure that
> * every task struct that event->ctx->task could possibly point to
> - * remains valid. This condition is satisifed when called through
> + * remains valid. This condition is satisfied when called through
> * perf_event_for_each_child or perf_event_for_each because they
> * hold the top-level event's child_mutex, so any descendant that
> * goes to exit will block in perf_event_exit_event().
> @@ -6054,7 +6054,7 @@ static void perf_sample_regs_intr(struct perf_regs *regs_intr,
> * Get remaining task size from user stack pointer.
> *
> * It'd be better to take stack vma map and limit this more
> - * precisly, but there's no way to get it safely under interrupt,
> + * precisely, but there's no way to get it safely under interrupt,
> * so using TASK_SIZE as limit.
> */
> static u64 perf_ustack_task_size(struct pt_regs *regs)
> @@ -6616,7 +6616,7 @@ void perf_prepare_sample(struct perf_event_header *header,
>
> if (sample_type & PERF_SAMPLE_STACK_USER) {
> /*
> - * Either we need PERF_SAMPLE_STACK_USER bit to be allways
> + * Either we need PERF_SAMPLE_STACK_USER bit to be always
> * processed as the last one or have additional check added
> * in case new sample type is added, because we could eat
> * up the rest of the sample size.
> --
> 2.20.1
--
- Arnaldo
next prev parent reply other threads:[~2019-09-20 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 17:12 [PATCH] perf/core: fixing several typos in comments Roy Ben Shlomo
2019-09-20 19:06 ` Arnaldo Carvalho de Melo [this message]
2019-09-22 10:52 ` [tip: perf/urgent] perf/core: Fix " tip-bot2 for Roy Ben Shlomo
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=20190920190656.GH4865@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=roy.benshlomo@gmail.com \
--cc=royb@sentinelone.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;
as well as URLs for NNTP newsgroup(s).