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 v2 0/2] Print map ID on successful creation
Date: Sat, 1 Nov 2025 16:59:47 +0000 [thread overview]
Message-ID: <5f7078cc-dc32-4d7a-888e-922efcba43b6@kernel.org> (raw)
In-Reply-To: <20251030210655.3938262-1-harshit.m.mogalapalli@oracle.com>
2025-10-30 14:06 UTC-0700 ~ Harshit Mogalapalli
<harshit.m.mogalapalli@oracle.com>
> Hi all,
>
> I have tried looking at an issue from the bpftool repository:
> https://github.com/libbpf/bpftool/issues/121 and this RFC tries to add
This is not longer a RFC :)
> that enhancement.
>
> Summary: Currently when a map creation is successful there is no message
> on the terminal, printing IDs on successful creation of maps can help
> notify the user and can be used in CI/CD.
>
> The first patch adds the logic for printing and the second patch adds a
> simple selftest for the same.
>
> The github issue is not fully solved with these two patches, as there
> are other bpf objects that might need similar additions. Would
> appreciate any inputs on this.
What's your question, exactly?
Thanks,
Quentin
next prev parent reply other threads:[~2025-11-01 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 21:06 [PATCH v2 0/2] Print map ID on successful creation Harshit Mogalapalli
2025-10-30 21:06 ` [PATCH v2 1/2] bpftool: Print map ID upon creation and support JSON output Harshit Mogalapalli
2025-10-31 5:21 ` Yonghong Song
2025-11-01 16:59 ` Quentin Monnet
2025-11-01 18:46 ` Harshit Mogalapalli
2025-10-30 21:06 ` [PATCH v2 2/2] selftests/bpf: Add test for bpftool map ID printing Harshit Mogalapalli
2025-11-01 16:59 ` Quentin Monnet
2025-11-01 16:59 ` Quentin Monnet [this message]
2025-11-01 19:20 ` [PATCH v2 0/2] Print map ID on successful creation Harshit Mogalapalli
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=5f7078cc-dc32-4d7a-888e-922efcba43b6@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