From: Quentin Monnet <qmo@kernel.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
bpf@vger.kernel.org
Cc: alan.maguire@oracle.com, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 2/2] selftests/bpf: Add test for bpftool map ID printing
Date: Mon, 3 Nov 2025 14:31:35 +0000 [thread overview]
Message-ID: <f8e1ee1d-5750-48ed-bdff-97664484910b@kernel.org> (raw)
In-Reply-To: <20251101193357.111186-3-harshit.m.mogalapalli@oracle.com>
On 01/11/2025 19:33, Harshit Mogalapalli wrote:
> Add selftest to check if Map ID is printed on successful creation in
> both plain text and json formats.
>
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Reviewed-by: Quentin Monnet <qmo@kernel.org>
Thank you!
prev parent reply other threads:[~2025-11-03 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 19:33 [PATCH v3 0/2] Print map ID on successful creation Harshit Mogalapalli
2025-11-01 19:33 ` [PATCH v3 1/2] bpftool: Print map ID upon creation and support JSON output Harshit Mogalapalli
2025-11-04 17:54 ` Alexei Starovoitov
2025-11-05 9:37 ` Quentin Monnet
2025-11-06 1:29 ` Alexei Starovoitov
2025-11-06 2:05 ` Quentin Monnet
2025-11-06 2:14 ` Alexei Starovoitov
2025-11-06 2:25 ` Quentin Monnet
2025-11-06 13:12 ` Harshit Mogalapalli
2025-11-01 19:33 ` [PATCH v3 2/2] selftests/bpf: Add test for bpftool map ID printing Harshit Mogalapalli
2025-11-03 14:31 ` Quentin Monnet [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=f8e1ee1d-5750-48ed-bdff-97664484910b@kernel.org \
--to=qmo@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox