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 0/3] bpftool: update documentation and fix checks
Date: Tue, 16 Nov 2021 13:00:09 +0000 [thread overview]
Message-ID: <163706760927.10284.10367416441736723127.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211115225844.33943-1-quentin@isovalent.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 15 Nov 2021 22:58:41 +0000 you wrote:
> This set updates the list of options for bpftool commands, as displayed in
> the summary of the man pages. It also updates the script that checks those
> option lists, to make it more robust, and more reusable if the layout of
> bpftool's directory changed.
>
> Checkpatch complained about the missing SPDX tag when I added a new file
> under bpftool/Documentation; I fixed it by adding the tag, and while at it,
> I also added the tags to all RST files for bpftool's documentation (see
> first patch of this set).
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpftool: Add SPDX tags to RST documentation files
https://git.kernel.org/bpf/bpf-next/c/4344842836e9
- [bpf-next,2/3] bpftool: Update doc (use susbtitutions) and test_bpftool_synctypes.py
https://git.kernel.org/bpf/bpf-next/c/b62318152040
- [bpf-next,3/3] selftests/bpf: Configure dir paths via env in test_bpftool_synctypes.py
https://git.kernel.org/bpf/bpf-next/c/e12cd158c8a4
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-11-16 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 22:58 [PATCH bpf-next 0/3] bpftool: update documentation and fix checks Quentin Monnet
2021-11-15 22:58 ` [PATCH bpf-next 1/3] bpftool: Add SPDX tags to RST documentation files Quentin Monnet
2021-11-15 22:58 ` [PATCH bpf-next 2/3] bpftool: Update doc (use susbtitutions) and test_bpftool_synctypes.py Quentin Monnet
2021-11-15 22:58 ` [PATCH bpf-next 3/3] selftests/bpf: Configure dir paths via env in test_bpftool_synctypes.py Quentin Monnet
2021-11-16 13: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=163706760927.10284.10367416441736723127.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).