From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@meta.com, thinker.li@gmail.com
Subject: Re: [PATCH v2 bpf-next] libbpf: Ensure undefined bpf_attr field stays 0
Date: Wed, 24 Jan 2024 23:20:24 +0000 [thread overview]
Message-ID: <170613842475.28029.9014326084721242761.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240124224418.2905133-1-martin.lau@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 24 Jan 2024 14:44:18 -0800 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> The commit 9e926acda0c2 ("libbpf: Find correct module BTFs for struct_ops maps and progs.")
> sets a newly added field (value_type_btf_obj_fd) to -1 in libbpf when
> the caller of the libbpf's bpf_map_create did not define this field by
> passing a NULL "opts" or passing in a "opts" that does not cover this
> new field. OPT_HAS(opts, field) is used to decide if the field is
> defined or not:
>
> [...]
Here is the summary with links:
- [v2,bpf-next] libbpf: Ensure undefined bpf_attr field stays 0
https://git.kernel.org/bpf/bpf-next/c/77c03cf314b4
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:[~2024-01-24 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 22:44 [PATCH v2 bpf-next] libbpf: Ensure undefined bpf_attr field stays 0 Martin KaFai Lau
2024-01-24 23: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=170613842475.28029.9014326084721242761.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=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=thinker.li@gmail.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