From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: shaomin Deng <dengshaomin@cdjrlc.com>
Cc: peterz@infradead.org, mingo@redhat.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf test: Fix typo in comments
Date: Fri, 12 Aug 2022 16:44:18 -0300 [thread overview]
Message-ID: <YvatkpgGPbbI6JsI@kernel.org> (raw)
In-Reply-To: <20220807074753.7857-1-dengshaomin@cdjrlc.com>
Em Sun, Aug 07, 2022 at 03:47:53AM -0400, shaomin Deng escreveu:
> Delete the rebundant word "then" in comments.
Thanks, applied.
- Arnaldo
> Signed-off-by: shaomin Deng <dengshaomin@cdjrlc.com>
> ---
> tools/perf/tests/perf-time-to-tsc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/perf-time-to-tsc.c b/tools/perf/tests/perf-time-to-tsc.c
> index 4ad0dfbc8b21..79a0d7fc6522 100644
> --- a/tools/perf/tests/perf-time-to-tsc.c
> +++ b/tools/perf/tests/perf-time-to-tsc.c
> @@ -64,7 +64,7 @@ static int test__tsc_is_supported(struct test_suite *test __maybe_unused,
> * This function implements a test that checks that the conversion of perf time
> * to and from TSC is consistent with the order of events. If the test passes
> * %0 is returned, otherwise %-1 is returned. If TSC conversion is not
> - * supported then then the test passes but " (not supported)" is printed.
> + * supported then the test passes but " (not supported)" is printed.
> */
> static int test__perf_time_to_tsc(struct test_suite *test __maybe_unused, int subtest __maybe_unused)
> {
> --
> 2.35.1
--
- Arnaldo
prev parent reply other threads:[~2022-08-12 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 7:47 [PATCH] perf test: Fix typo in comments shaomin Deng
2022-08-12 19:44 ` 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=YvatkpgGPbbI6JsI@kernel.org \
--to=acme@kernel.org \
--cc=dengshaomin@cdjrlc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 NNTP newsgroup(s).