From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jilin Yuan <yuanjilin@cdjrlc.com>
Cc: peterz@infradead.org, mingo@redhat.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/perf: fix repeated words in comments
Date: Mon, 22 Aug 2022 11:06:04 -0300 [thread overview]
Message-ID: <YwONTFjom5v6Y1T/@kernel.org> (raw)
In-Reply-To: <20220822123919.32547-1-yuanjilin@cdjrlc.com>
Em Mon, Aug 22, 2022 at 08:39:19PM +0800, Jilin Yuan escreveu:
> Delete the redundant word 'and'.
Applied already https://lore.kernel.org/lkml/20220807084629.23121-1-dengshaomin@cdjrlc.com/
> Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
> ---
> tools/perf/builtin-trace.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index 897fc504918b..2f7b1111d8e9 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -2040,7 +2040,7 @@ static size_t syscall__scnprintf_args(struct syscall *sc, char *bf, size_t size,
>
> /*
> * Suppress this argument if its value is zero and
> - * and we don't have a string associated in an
> + * we don't have a string associated in an
> * strarray for it.
> */
> if (val == 0 &&
> @@ -2748,7 +2748,7 @@ static size_t trace__fprintf_tp_fields(struct trace *trace, struct evsel *evsel,
>
> /*
> * Suppress this argument if its value is zero and
> - * and we don't have a string associated in an
> + * we don't have a string associated in an
> * strarray for it.
> */
> if (val == 0 &&
> --
> 2.36.1
--
- Arnaldo
prev parent reply other threads:[~2022-08-22 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 12:39 [PATCH] tools/perf: fix repeated words in comments Jilin Yuan
2022-08-22 14:06 ` 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=YwONTFjom5v6Y1T/@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yuanjilin@cdjrlc.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.