From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Ali Zahraee <ahzahraee@gmail.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests: ftrace: fix typo in test report
Date: Tue, 6 Feb 2024 22:35:54 +0900 [thread overview]
Message-ID: <20240206223554.719c004c6fe2f6c44aa81ef9@kernel.org> (raw)
In-Reply-To: <20240201082557.15965-1-ahzahraee@gmail.com>
On Thu, 1 Feb 2024 09:25:57 +0100
Ali Zahraee <ahzahraee@gmail.com> wrote:
> This is just another trivial typo fix. The typo shows up in the final
> report after tests are done.
>
Thanks, and that is already reported very recently.
https://lore.kernel.org/all/20240129162841.57979-1-five231003@gmail.com/
> Signed-off-by: Ali Zahraee <ahzahraee@gmail.com>
> ---
> tools/testing/selftests/ftrace/ftracetest | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest
> index c778d4dcc17e..25d4e0fca385 100755
> --- a/tools/testing/selftests/ftrace/ftracetest
> +++ b/tools/testing/selftests/ftrace/ftracetest
> @@ -504,7 +504,7 @@ prlog "# of undefined(test bug): " `echo $UNDEFINED_CASES | wc -w`
> if [ "$KTAP" = "1" ]; then
> echo -n "# Totals:"
> echo -n " pass:"`echo $PASSED_CASES | wc -w`
> - echo -n " faii:"`echo $FAILED_CASES | wc -w`
> + echo -n " fail:"`echo $FAILED_CASES | wc -w`
> echo -n " xfail:"`echo $XFAILED_CASES | wc -w`
> echo -n " xpass:0"
> echo -n " skip:"`echo $UNTESTED_CASES $UNSUPPORTED_CASES | wc -w`
> --
> 2.34.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2024-02-06 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 8:25 [PATCH] selftests: ftrace: fix typo in test report Ali Zahraee
2024-02-01 9:40 ` Kousik Sanagavarapu
2024-02-06 13:35 ` Masami Hiramatsu [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=20240206223554.719c004c6fe2f6c44aa81ef9@kernel.org \
--to=mhiramat@kernel.org \
--cc=ahzahraee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=shuah@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