From: patchwork-bot+netdevbpf@kernel.org
To: Roberto Sassu <roberto.sassu@huaweicloud.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
roberto.sassu@huawei.com
Subject: Re: [PATCH v2 0/6] Add _opts variant for bpf_*_get_fd_by_id()
Date: Tue, 11 Oct 2022 00:20:16 +0000 [thread overview]
Message-ID: <166544761611.23458.18371986973168379467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221006110736.84253-1-roberto.sassu@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 6 Oct 2022 13:07:30 +0200 you wrote:
> From: Roberto Sassu <roberto.sassu@huawei.com>
>
> Add the _opts variant for bpf_*_get_fd_by_id() functions, to be able to
> pass to the kernel more options, when requesting a fd of an eBPF object.
>
> Pass the options through a newly introduced structure,
> bpf_get_fd_by_id_opts, which currently contains open_flags (the other two
> members are for compatibility and for padding).
>
> [...]
Here is the summary with links:
- [v2,1/6] libbpf: Fix LIBBPF_1.0.0 declaration in libbpf.map
https://git.kernel.org/bpf/bpf-next/c/7a366da2d2ba
- [v2,2/6] libbpf: Introduce bpf_get_fd_by_id_opts and bpf_map_get_fd_by_id_opts()
https://git.kernel.org/bpf/bpf-next/c/243e300563b1
- [v2,3/6] libbpf: Introduce bpf_prog_get_fd_by_id_opts()
https://git.kernel.org/bpf/bpf-next/c/8f13f168ea14
- [v2,4/6] libbpf: Introduce bpf_btf_get_fd_by_id_opts()
https://git.kernel.org/bpf/bpf-next/c/2ce7cbf2ba71
- [v2,5/6] libbpf: Introduce bpf_link_get_fd_by_id_opts()
https://git.kernel.org/bpf/bpf-next/c/97c8f9dd5db8
- [v2,6/6] selftests/bpf: Add tests for _opts variants of bpf_*_get_fd_by_id()
https://git.kernel.org/bpf/bpf-next/c/a9c7c18b5759
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-10-11 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 11:07 [PATCH v2 0/6] Add _opts variant for bpf_*_get_fd_by_id() Roberto Sassu
2022-10-06 11:07 ` [PATCH v2 1/6] libbpf: Fix LIBBPF_1.0.0 declaration in libbpf.map Roberto Sassu
2022-10-06 11:07 ` [PATCH v2 2/6] libbpf: Introduce bpf_get_fd_by_id_opts and bpf_map_get_fd_by_id_opts() Roberto Sassu
2022-10-06 11:07 ` [PATCH v2 3/6] libbpf: Introduce bpf_prog_get_fd_by_id_opts() Roberto Sassu
2022-10-06 11:07 ` [PATCH v2 4/6] libbpf: Introduce bpf_btf_get_fd_by_id_opts() Roberto Sassu
2022-10-06 11:07 ` [PATCH v2 5/6] libbpf: Introduce bpf_link_get_fd_by_id_opts() Roberto Sassu
2022-10-06 11:07 ` [PATCH v2 6/6] selftests/bpf: Add tests for _opts variants of bpf_*_get_fd_by_id() Roberto Sassu
2022-10-07 10:59 ` [PATCH v2 0/6] Add _opts variant for bpf_*_get_fd_by_id() Jiri Olsa
2022-10-07 11:31 ` Roberto Sassu
2022-10-11 0:20 ` 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=166544761611.23458.18371986973168379467.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=haoluo@google.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=mykolal@fb.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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.