From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, mykolal@fb.com,
jose.marchesi@oracle.com
Subject: Re: [PATCH bpf-next v3 0/6] BTF: arbitrary __attribute__ encoding
Date: Thu, 06 Feb 2025 01:00:33 +0000 [thread overview]
Message-ID: <173880363326.959069.4707220911950424811.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250130201239.1429648-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 30 Jan 2025 12:12:33 -0800 you wrote:
> This patch series extends BPF Type Format (BTF) to support arbitrary
> __attribute__ encoding.
>
> Setting the kind_flag to 1 in BTF type tags and decl tags now changes
> the meaning for the encoded tag, in particular with respect to
> btf_dump in libbpf.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/6] libbpf: introduce kflag for type_tags and decl_tags in BTF
https://git.kernel.org/bpf/bpf-next/c/51d1b1d42841
- [bpf-next,v3,2/6] docs/bpf: document the semantics of BTF tags with kind_flag
https://git.kernel.org/bpf/bpf-next/c/ea70faa1f244
- [bpf-next,v3,3/6] libbpf: check the kflag of type tags in btf_dump
https://git.kernel.org/bpf/bpf-next/c/2019c58318b8
- [bpf-next,v3,4/6] selftests/bpf: add a btf_dump test for type_tags
https://git.kernel.org/bpf/bpf-next/c/6c2d2a05a762
- [bpf-next,v3,5/6] bpf: allow kind_flag for BTF type and decl tags
https://git.kernel.org/bpf/bpf-next/c/53ee0d66d7a6
- [bpf-next,v3,6/6] selftests/bpf: add a BTF verification test for kflagged type_tag
https://git.kernel.org/bpf/bpf-next/c/770cdcf4a59e
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:[~2025-02-06 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 20:12 [PATCH bpf-next v3 0/6] BTF: arbitrary __attribute__ encoding Ihor Solodrai
2025-01-30 20:12 ` [PATCH bpf-next v3 1/6] libbpf: introduce kflag for type_tags and decl_tags in BTF Ihor Solodrai
2025-01-30 20:12 ` [PATCH bpf-next v3 2/6] docs/bpf: document the semantics of BTF tags with kind_flag Ihor Solodrai
2025-01-30 20:12 ` [PATCH bpf-next v3 3/6] libbpf: check the kflag of type tags in btf_dump Ihor Solodrai
2025-01-30 20:12 ` [PATCH bpf-next v3 4/6] selftests/bpf: add a btf_dump test for type_tags Ihor Solodrai
2025-01-30 20:12 ` [PATCH bpf-next v3 5/6] bpf: allow kind_flag for BTF type and decl tags Ihor Solodrai
2025-01-31 2:55 ` Eduard Zingerman
2025-01-31 3:55 ` Ihor Solodrai
2025-01-30 20:12 ` [PATCH bpf-next v3 6/6] selftests/bpf: add a BTF verification test for kflagged type_tag Ihor Solodrai
2025-02-06 1: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=173880363326.959069.4707220911950424811.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=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=jose.marchesi@oracle.com \
--cc=mykolal@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