Linux-perf-users Archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] perf record: Fix comment misspellings
Date: Thu, 25 Apr 2024 11:21:08 -0300	[thread overview]
Message-ID: <Zipm1B6qZ1NFANAc@x1> (raw)
In-Reply-To: <20240425060427.1800663-1-howardchu95@gmail.com>

On Thu, Apr 25, 2024 at 02:04:27PM +0800, Howard Chu wrote:
> Fix comment misspellings

Thanks, applied to perf-tools-next,

- Arnaldo
 
> Signed-off-by: Howard Chu <howardchu95@gmail.com>
> ---
>  tools/lib/perf/mmap.c       | 2 +-
>  tools/perf/builtin-record.c | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/lib/perf/mmap.c b/tools/lib/perf/mmap.c
> index 0c903c2372c9..c1a51d925e0e 100644
> --- a/tools/lib/perf/mmap.c
> +++ b/tools/lib/perf/mmap.c
> @@ -279,7 +279,7 @@ union perf_event *perf_mmap__read_event(struct perf_mmap *map)
>  	if (!refcount_read(&map->refcnt))
>  		return NULL;
>  
> -	/* non-overwirte doesn't pause the ringbuffer */
> +	/* non-overwrite doesn't pause the ringbuffer */
>  	if (!map->overwrite)
>  		map->end = perf_mmap__read_head(map);
>  
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 3994adaf4607..34d103f4af57 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -332,7 +332,7 @@ static int record__aio_complete(struct mmap *md, struct aiocb *cblock)
>  	} else {
>  		/*
>  		 * aio write request may require restart with the
> -		 * reminder if the kernel didn't write whole
> +		 * remainder if the kernel didn't write whole
>  		 * chunk at once.
>  		 */
>  		rem_off = cblock->aio_offset + written;
> @@ -402,7 +402,7 @@ static int record__aio_pushfn(struct mmap *map, void *to, void *buf, size_t size
>  	 *
>  	 * Coping can be done in two steps in case the chunk of profiling data
>  	 * crosses the upper bound of the kernel buffer. In this case we first move
> -	 * part of data from map->start till the upper bound and then the reminder
> +	 * part of data from map->start till the upper bound and then the remainder
>  	 * from the beginning of the kernel buffer till the end of the data chunk.
>  	 */
>  
> -- 
> 2.44.0

      reply	other threads:[~2024-04-25 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  6:04 [PATCH] perf record: Fix comment misspellings Howard Chu
2024-04-25 14:21 ` Arnaldo Carvalho de Melo [this message]

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=Zipm1B6qZ1NFANAc@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=trivial@kernel.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).