From: Leon Hwang <leon.hwang@linux.dev>
To: Tao Chen <chen.dylane@linux.dev>, bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, yatsenko@meta.com, puranjay@kernel.org,
davidzalman.101@gmail.com, cheick.traore@foss.st.com,
mika.westerberg@linux.intel.com, ameryhung@gmail.com,
menglong8.dong@gmail.com, kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v2 3/3] selftests/bpf: Add union argument tests using fexit programs
Date: Fri, 19 Sep 2025 09:47:06 +0800 [thread overview]
Message-ID: <bd40f8ce-37ed-48b0-b2ad-69eff76a4c20@linux.dev> (raw)
In-Reply-To: <dbea9a14-e010-4e2f-a34d-4e2fd14a31f6@linux.dev>
On 19/9/25 00:09, Tao Chen wrote:
> 在 2025/9/16 23:52, Leon Hwang 写道:
>> By referencing
>> commit 1642a3945e223 ("selftests/bpf: Add struct argument tests with
>> fentry/fexit programs."),
>> test the following cases for union argument support:
>>
>
> Can we use ‘commit 1642a3945e22’ with 12 chars, maybe it's minor nit
> anyways or not.
>
Thank you for pointing this out.
I’ll update my script to generate the commit information in the proper
format.
Thanks,
Leon
next prev parent reply other threads:[~2025-09-19 1:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 15:52 [PATCH bpf-next v2 0/3] bpf: Allow union argument in trampoline based programs Leon Hwang
2025-09-16 15:52 ` [PATCH bpf-next v2 1/3] " Leon Hwang
2025-09-16 21:35 ` Amery Hung
2025-09-17 12:40 ` Leon Hwang
2025-09-17 18:13 ` Alexei Starovoitov
2025-09-18 1:47 ` Leon Hwang
2025-09-16 15:52 ` [PATCH bpf-next v2 2/3] bpf, x64: Add union argument support in trampoline Leon Hwang
2025-09-16 15:52 ` [PATCH bpf-next v2 3/3] selftests/bpf: Add union argument tests using fexit programs Leon Hwang
2025-09-18 16:09 ` Tao Chen
2025-09-19 1:47 ` Leon Hwang [this message]
2025-09-19 1:53 ` Alexei Starovoitov
2025-09-19 2:01 ` Leon Hwang
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=bd40f8ce-37ed-48b0-b2ad-69eff76a4c20@linux.dev \
--to=leon.hwang@linux.dev \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cheick.traore@foss.st.com \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=davidzalman.101@gmail.com \
--cc=eddyz87@gmail.com \
--cc=kernel-patches-bot@fb.com \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=puranjay@kernel.org \
--cc=song@kernel.org \
--cc=yatsenko@meta.com \
--cc=yonghong.song@linux.dev \
/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.