From: patchwork-bot+netdevbpf@kernel.org
To: Milan Landaverde <milan@mdaverde.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
quentin@isovalent.com, davemarchevsky@fb.com, sdf@google.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/3] bpf/bpftool: add program & link type names
Date: Mon, 04 Apr 2022 22:00:12 +0000 [thread overview]
Message-ID: <164910961287.9198.15493484782582788851.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220331154555.422506-1-milan@mdaverde.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 31 Mar 2022 11:45:52 -0400 you wrote:
> With the addition of the syscall prog type we should now
> be able to see feature probe info for that prog type:
>
> $ bpftool feature probe kernel
> ...
> eBPF program_type syscall is available
> ...
> eBPF helpers supported for program type syscall:
> ...
> - bpf_sys_bpf
> - bpf_sys_close
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpf/bpftool: add syscall prog type
https://git.kernel.org/bpf/bpf-next/c/380341637ebb
- [bpf-next,2/3] bpf/bpftool: add missing link types
https://git.kernel.org/bpf/bpf-next/c/fff3dfab1786
- [bpf-next,3/3] bpf/bpftool: handle libbpf_probe_prog_type errors
https://git.kernel.org/bpf/bpf-next/c/7b53eaa656c3
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-04-04 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 15:45 [PATCH bpf-next 0/3] bpf/bpftool: add program & link type names Milan Landaverde
2022-03-31 15:45 ` [PATCH bpf-next 1/3] bpf/bpftool: add syscall prog type Milan Landaverde
2022-04-01 16:04 ` Quentin Monnet
2022-04-01 18:40 ` Andrii Nakryiko
2022-04-01 21:20 ` Quentin Monnet
2022-03-31 15:45 ` [PATCH bpf-next 2/3] bpf/bpftool: add missing link types Milan Landaverde
2022-04-01 16:05 ` Quentin Monnet
2022-04-04 21:55 ` Andrii Nakryiko
2022-03-31 15:45 ` [PATCH bpf-next 3/3] bpf/bpftool: handle libbpf_probe_prog_type errors Milan Landaverde
2022-04-01 16:05 ` Quentin Monnet
2022-04-01 18:42 ` Andrii Nakryiko
2022-04-01 21:33 ` Quentin Monnet
2022-04-03 23:51 ` Andrii Nakryiko
2022-04-04 22:00 ` 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=164910961287.9198.15493484782582788851.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milan@mdaverde.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox