From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Monnet <quentin@isovalent.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/7] tools: bpftool: update, synchronise and validate types and options
Date: Fri, 30 Jul 2021 22:50:06 +0000 [thread overview]
Message-ID: <162768540695.9078.16392492200639204040.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210730215435.7095-1-quentin@isovalent.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 30 Jul 2021 22:54:28 +0100 you wrote:
> To work with the different program types, map types, attach types etc.
> supported by eBPF, bpftool needs occasional updates to learn about the new
> features supported by the kernel. When such types translate into new
> keyword for the command line, updates are expected in several locations:
> typically, the help message displayed from bpftool itself, the manual page,
> and the bash completion file should be updated. The options used by the
> different commands for bpftool should also remain synchronised at those
> locations.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/7] tools: bpftool: slightly ease bash completion updates
https://git.kernel.org/bpf/bpf-next/c/510b4d4c5d4c
- [bpf-next,v2,2/7] selftests/bpf: check consistency between bpftool source, doc, completion
https://git.kernel.org/bpf/bpf-next/c/a2b5944fb4e0
- [bpf-next,v2,3/7] tools: bpftool: complete and synchronise attach or map types
https://git.kernel.org/bpf/bpf-next/c/b544342e52fc
- [bpf-next,v2,4/7] tools: bpftool: update and synchronise option list in doc and help msg
https://git.kernel.org/bpf/bpf-next/c/c07ba629df97
- [bpf-next,v2,5/7] selftests/bpf: update bpftool's consistency script for checking options
https://git.kernel.org/bpf/bpf-next/c/da87772f086f
- [bpf-next,v2,6/7] tools: bpftool: document and add bash completion for -L, -B options
https://git.kernel.org/bpf/bpf-next/c/8cc8c6357c8f
- [bpf-next,v2,7/7] tools: bpftool: complete metrics list in "bpftool prog profile" doc
https://git.kernel.org/bpf/bpf-next/c/475a23c2c15f
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:[~2021-07-30 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 21:54 [PATCH bpf-next v2 0/7] tools: bpftool: update, synchronise and validate types and options Quentin Monnet
2021-07-30 21:54 ` [PATCH bpf-next v2 1/7] tools: bpftool: slightly ease bash completion updates Quentin Monnet
2021-07-30 21:54 ` [PATCH bpf-next v2 2/7] selftests/bpf: check consistency between bpftool source, doc, completion Quentin Monnet
2021-07-30 21:54 ` [PATCH bpf-next v2 3/7] tools: bpftool: complete and synchronise attach or map types Quentin Monnet
2021-07-30 21:54 ` [PATCH bpf-next v2 4/7] tools: bpftool: update and synchronise option list in doc and help msg Quentin Monnet
2021-07-30 21:54 ` [PATCH bpf-next v2 5/7] selftests/bpf: update bpftool's consistency script for checking options Quentin Monnet
2021-07-30 21:54 ` [PATCH bpf-next v2 6/7] tools: bpftool: document and add bash completion for -L, -B options Quentin Monnet
2021-07-30 21:54 ` [PATCH bpf-next v2 7/7] tools: bpftool: complete metrics list in "bpftool prog profile" doc Quentin Monnet
2021-07-30 22: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=162768540695.9078.16392492200639204040.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=netdev@vger.kernel.org \
--cc=quentin@isovalent.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;
as well as URLs for NNTP newsgroup(s).