From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Monnet <quentin@isovalent.com>
Cc: 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, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpftool: Add "bootstrap" feature to version output
Date: Fri, 21 Oct 2022 21:50:16 +0000 [thread overview]
Message-ID: <166638901694.27641.3547797661599408874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221020100332.69563-1-quentin@isovalent.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 20 Oct 2022 11:03:32 +0100 you wrote:
> Along with the version number, "bpftool version" displays a list of
> features that were selected at compilation time for bpftool. It would be
> useful to indicate in that list whether a binary is a bootstrap version
> of bpftool. Given that an increasing number of components rely on
> bootstrap versions for generating skeletons, this could help understand
> what a binary is capable of if it has been copied outside of the usual
> "bootstrap" directory.
>
> [...]
Here is the summary with links:
- [bpf-next] bpftool: Add "bootstrap" feature to version output
https://git.kernel.org/bpf/bpf-next/c/2c76238eaddd
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-21 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 10:03 [PATCH bpf-next] bpftool: Add "bootstrap" feature to version output Quentin Monnet
2022-10-21 21:50 ` 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=166638901694.27641.3547797661599408874.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=kafai@fb.com \
--cc=kpsingh@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