All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	namhyung@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH -next] perf doc: Fix typo in perf.data-file-format.txt
Date: Thu, 27 Jul 2023 10:07:55 -0300	[thread overview]
Message-ID: <ZMJsK3eWvDcCRAqQ@kernel.org> (raw)
In-Reply-To: <20230727105001.261420-1-xiujianfeng@huawei.com>

Em Thu, Jul 27, 2023 at 10:50:01AM +0000, Xiu Jianfeng escreveu:
> The 'it' should be 'is' here, fix it.

Thanks, applied.

- Arnaldo

 
> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
> ---
>  tools/perf/Documentation/perf.data-file-format.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/Documentation/perf.data-file-format.txt b/tools/perf/Documentation/perf.data-file-format.txt
> index 635ba043fd7d..010a4edcd384 100644
> --- a/tools/perf/Documentation/perf.data-file-format.txt
> +++ b/tools/perf/Documentation/perf.data-file-format.txt
> @@ -43,7 +43,7 @@ struct perf_file_section {
>  
>  Flags section:
>  
> -For each of the optional features a perf_file_section it placed after the data
> +For each of the optional features a perf_file_section is placed after the data
>  section if the feature bit is set in the perf_header flags bitset. The
>  respective perf_file_section points to the data of the additional header and
>  defines its size.
> -- 
> 2.34.1

      reply	other threads:[~2023-07-27 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 10:50 [PATCH -next] perf doc: Fix typo in perf.data-file-format.txt Xiu Jianfeng
2023-07-27 13:07 ` 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=ZMJsK3eWvDcCRAqQ@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@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=xiujianfeng@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.