From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, yhs@fb.com,
quentin@isovalent.com
Subject: Re: [PATCH bpf-next v4 00/12] libbpf: Textual representation of enums
Date: Tue, 31 May 2022 21:40:22 +0000 [thread overview]
Message-ID: <165403322252.3055.5094237402728093213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220523230428.3077108-1-deso@posteo.net>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 23 May 2022 23:04:16 +0000 you wrote:
> This patch set introduces the means for querying a textual representation of
> the following BPF related enum types:
> - enum bpf_map_type
> - enum bpf_prog_type
> - enum bpf_attach_type
> - enum bpf_link_type
>
> [...]
Here is the summary with links:
- [bpf-next,v4,01/12] libbpf: Introduce libbpf_bpf_prog_type_str
https://git.kernel.org/bpf/bpf-next/c/36f21676bad3
- [bpf-next,v4,02/12] selftests/bpf: Add test for libbpf_bpf_prog_type_str
https://git.kernel.org/bpf/bpf-next/c/9bb1be5c6eed
- [bpf-next,v4,03/12] bpftool: Use libbpf_bpf_prog_type_str
https://git.kernel.org/bpf/bpf-next/c/13259b23955f
- [bpf-next,v4,04/12] libbpf: Introduce libbpf_bpf_map_type_str
https://git.kernel.org/bpf/bpf-next/c/1be3ac58c1f7
- [bpf-next,v4,05/12] selftests/bpf: Add test for libbpf_bpf_map_type_str
https://git.kernel.org/bpf/bpf-next/c/4714649a9af8
- [bpf-next,v4,06/12] bpftool: Use libbpf_bpf_map_type_str
https://git.kernel.org/bpf/bpf-next/c/889f4cba4bdb
- [bpf-next,v4,07/12] libbpf: Introduce libbpf_bpf_attach_type_str
https://git.kernel.org/bpf/bpf-next/c/58342919a189
- [bpf-next,v4,08/12] selftests/bpf: Add test for libbpf_bpf_attach_type_str
https://git.kernel.org/bpf/bpf-next/c/98e0e5eb4412
- [bpf-next,v4,09/12] bpftool: Use libbpf_bpf_attach_type_str
https://git.kernel.org/bpf/bpf-next/c/2a5ada03fcb3
- [bpf-next,v4,10/12] libbpf: Introduce libbpf_bpf_link_type_str
https://git.kernel.org/bpf/bpf-next/c/19b4ce1e29ff
- [bpf-next,v4,11/12] selftests/bpf: Add test for libbpf_bpf_link_type_str
https://git.kernel.org/bpf/bpf-next/c/8ff2d074f953
- [bpf-next,v4,12/12] bpftool: Use libbpf_bpf_link_type_str
https://git.kernel.org/bpf/bpf-next/c/9522b20b46c3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-31 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 23:04 [PATCH bpf-next v4 00/12] libbpf: Textual representation of enums Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 01/12] libbpf: Introduce libbpf_bpf_prog_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 02/12] selftests/bpf: Add test for libbpf_bpf_prog_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 03/12] bpftool: Use libbpf_bpf_prog_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 04/12] libbpf: Introduce libbpf_bpf_map_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 05/12] selftests/bpf: Add test for libbpf_bpf_map_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 06/12] bpftool: Use libbpf_bpf_map_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 07/12] libbpf: Introduce libbpf_bpf_attach_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 08/12] selftests/bpf: Add test for libbpf_bpf_attach_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 09/12] bpftool: Use libbpf_bpf_attach_type_str Daniel Müller
2022-05-24 9:06 ` Quentin Monnet
2022-05-23 23:04 ` [PATCH bpf-next v4 10/12] libbpf: Introduce libbpf_bpf_link_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 11/12] selftests/bpf: Add test for libbpf_bpf_link_type_str Daniel Müller
2022-05-23 23:04 ` [PATCH bpf-next v4 12/12] bpftool: Use libbpf_bpf_link_type_str Daniel Müller
2022-05-31 21:40 ` patchwork-bot+netdevbpf [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=165403322252.3055.5094237402728093213.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=quentin@isovalent.com \
--cc=yhs@fb.com \
/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.