From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Yu Liao <liaoyu15@huawei.com>
Cc: <linux-trace-kernel@vger.kernel.org>, <rostedt@goodmis.org>,
<shuah@kernel.org>, <liwei391@huawei.com>
Subject: Re: [PATCH -next 1/2] selftests/ftrace: add loongarch support for kprobe args char tests
Date: Wed, 16 Aug 2023 14:34:47 +0900 [thread overview]
Message-ID: <20230816143447.388a24617849383bc84b0e18@kernel.org> (raw)
In-Reply-To: <20230815085912.701356-2-liaoyu15@huawei.com>
On Tue, 15 Aug 2023 16:59:11 +0800
Yu Liao <liaoyu15@huawei.com> wrote:
> Add loongarch support for the recently added kprobe args tests.
>
Looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you,
> Signed-off-by: Yu Liao <liaoyu15@huawei.com>
> ---
> .../testing/selftests/ftrace/test.d/kprobe/kprobe_args_char.tc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_char.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_char.tc
> index 285b4770efad..3047fa96a7b7 100644
> --- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_char.tc
> +++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_char.tc
> @@ -28,6 +28,9 @@ s390*)
> mips*)
> ARG1=%r4
> ;;
> +loongarch*)
> + ARG1=%r4
> +;;
> *)
> echo "Please implement other architecture here"
> exit_untested
> --
> 2.25.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-08-16 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 8:59 [PATCH -next 0/2] add loongarch and riscv support for kprobe args test Yu Liao
2023-08-15 8:59 ` [PATCH -next 1/2] selftests/ftrace: add loongarch support for kprobe args char tests Yu Liao
2023-08-16 5:34 ` Masami Hiramatsu [this message]
2023-08-15 8:59 ` [PATCH -next 2/2] selftests/ftrace: Add riscv support for kprobe arg tests Yu Liao
2023-08-16 5:35 ` Masami Hiramatsu
2023-10-17 17:37 ` [PATCH -next 0/2] add loongarch and riscv support for kprobe args test Steven Rostedt
2023-10-17 23:58 ` Shuah Khan
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=20230816143447.388a24617849383bc84b0e18@kernel.org \
--to=mhiramat@kernel.org \
--cc=liaoyu15@huawei.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=liwei391@huawei.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;
as well as URLs for NNTP newsgroup(s).