From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, qmo@kernel.org, andrii.nakryiko@gmail.com,
antony@phenome.org, toke@kernel.org, martin.lau@linux.dev
Subject: Re: [PATCH bpf-next v5 0/4] bpftool: btf: Support dumping a single type from file
Date: Fri, 13 Dec 2024 22:40:29 +0000 [thread overview]
Message-ID: <173412962995.3181069.4927934757783074209.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1734119028.git.dxu@dxuuu.xyz>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 13 Dec 2024 12:44:08 -0700 you wrote:
> Some projects, for example xdp-tools [0], prefer to check in a minimized
> vmlinux.h rather than the complete file which can get rather large.
>
> However, when you try to add a minimized version of a complex struct (eg
> struct xfrm_state), things can get quite complex if you're trying to
> manually untangle and deduplicate the dependencies.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/4] bpftool: man: Add missing format argument to command description
https://git.kernel.org/bpf/bpf-next/c/5e3ad22d8223
- [bpf-next,v5,2/4] bpftool: btf: Validate root_type_ids early
https://git.kernel.org/bpf/bpf-next/c/7f5819e1ace8
- [bpf-next,v5,3/4] bpftool: btf: Support dumping a specific types from file
https://git.kernel.org/bpf/bpf-next/c/a812d92ed2ae
- [bpf-next,v5,4/4] bpftool: bash: Add bash completion for root_id argument
https://git.kernel.org/bpf/bpf-next/c/9d294f698678
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-12-13 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:44 [PATCH bpf-next v5 0/4] bpftool: btf: Support dumping a single type from file Daniel Xu
2024-12-13 19:44 ` [PATCH bpf-next v5 1/4] bpftool: man: Add missing format argument to command description Daniel Xu
2024-12-13 19:44 ` [PATCH bpf-next v5 2/4] bpftool: btf: Validate root_type_ids early Daniel Xu
2024-12-13 19:44 ` [PATCH bpf-next v5 3/4] bpftool: btf: Support dumping a specific types from file Daniel Xu
2024-12-13 19:44 ` [PATCH bpf-next v5 4/4] bpftool: bash: Add bash completion for root_id argument Daniel Xu
2024-12-13 22: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=173412962995.3181069.4927934757783074209.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=antony@phenome.org \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=qmo@kernel.org \
--cc=toke@kernel.org \
/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.