From: Shuah <shuah@kernel.org>
To: Yu Liao <liaoyu15@huawei.com>, skhan@linuxfoundation.org
Cc: liwei391@huawei.com, rostedt@goodmis.org,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org,
mhiramat@kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [RESEND PATCH 0/2] add loongarch and riscv support for kprobe args test
Date: Wed, 18 Oct 2023 13:14:08 -0600 [thread overview]
Message-ID: <a802bb07-b7d3-4c8b-b0ff-77da021e63fa@kernel.org> (raw)
In-Reply-To: <20231018020858.1304218-1-liaoyu15@huawei.com>
On 10/17/23 20:08, Yu Liao wrote:
> Yu Liao (2):
> selftests/ftrace: add loongarch support for kprobe args char tests
> selftests/ftrace: Add riscv support for kprobe arg tests
>
> .../selftests/ftrace/test.d/kprobe/kprobe_args_char.tc | 6 ++++++
> .../selftests/ftrace/test.d/kprobe/kprobe_args_string.tc | 3 +++
> .../selftests/ftrace/test.d/kprobe/kprobe_args_syntax.tc | 4 ++++
> 3 files changed, 13 insertions(+)
>
Applied these two patches to linux-kselftest next for Linux 6.7-rc1.
thanks,
-- Shuah
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-10-18 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 2:08 [RESEND PATCH 0/2] add loongarch and riscv support for kprobe args test Yu Liao
2023-10-18 2:08 ` [RESEND PATCH 1/2] selftests/ftrace: add loongarch support for kprobe args char tests Yu Liao
2023-10-18 2:08 ` [RESEND PATCH 2/2] selftests/ftrace: Add riscv support for kprobe arg tests Yu Liao
2023-10-18 19:14 ` Shuah [this message]
2023-11-12 0:55 ` [RESEND PATCH 0/2] add loongarch and riscv support for kprobe args test patchwork-bot+linux-riscv
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=a802bb07-b7d3-4c8b-b0ff-77da021e63fa@kernel.org \
--to=shuah@kernel.org \
--cc=liaoyu15@huawei.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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