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,
vladimir.cunat@nic.cz
Subject: Re: [PATCH bpf-next] bpftool: Set binary name to "bpftool" in help and version output
Date: Fri, 21 Oct 2022 21:40:16 +0000 [thread overview]
Message-ID: <166638841645.20449.6790734622117237392.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221020100300.69328-1-quentin@isovalent.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 20 Oct 2022 11:03:00 +0100 you wrote:
> Commands "bpftool help" or "bpftool version" use argv[0] to display the
> name of the binary. While it is a convenient way to retrieve the string,
> it does not always produce the most readable output. For example,
> because of the way bpftool is currently packaged on Ubuntu (using a
> wrapper script), the command displays the absolute path for the binary:
>
> $ bpftool version | head -n 1
> /usr/lib/linux-tools/5.15.0-50-generic/bpftool v5.15.60
>
> [...]
Here is the summary with links:
- [bpf-next] bpftool: Set binary name to "bpftool" in help and version output
https://git.kernel.org/bpf/bpf-next/c/7e5eb725cf0a
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:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 10:03 [PATCH bpf-next] bpftool: Set binary name to "bpftool" in help and version output Quentin Monnet
2022-10-21 21: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=166638841645.20449.6790734622117237392.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=vladimir.cunat@nic.cz \
--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.