From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Monnet <qmo@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpftool: Add missing blank lines in bpftool-net doc example
Date: Mon, 02 Sep 2024 16:30:29 +0000 [thread overview]
Message-ID: <172529462950.3935899.5396247121344260485.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240901210742.25758-1-qmo@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 1 Sep 2024 22:07:42 +0100 you wrote:
> In bpftool-net documentation, two blank lines are missing in a
> recently added example, causing docutils to complain:
>
> $ cd tools/bpf/bpftool
> $ make doc
> DESCEND Documentation
> GEN bpftool-btf.8
> GEN bpftool-cgroup.8
> GEN bpftool-feature.8
> GEN bpftool-gen.8
> GEN bpftool-iter.8
> GEN bpftool-link.8
> GEN bpftool-map.8
> GEN bpftool-net.8
> <stdin>:189: (INFO/1) Possible incomplete section title.
> Treating the overline as ordinary text because it's so short.
> <stdin>:192: (INFO/1) Blank line missing before literal block (after the "::")? Interpreted as a definition list item.
> <stdin>:199: (INFO/1) Possible incomplete section title.
> Treating the overline as ordinary text because it's so short.
> <stdin>:201: (INFO/1) Blank line missing before literal block (after the "::")? Interpreted as a definition list item.
> GEN bpftool-perf.8
> GEN bpftool-prog.8
> GEN bpftool.8
> GEN bpftool-struct_ops.8
>
> [...]
Here is the summary with links:
- [bpf-next] bpftool: Add missing blank lines in bpftool-net doc example
https://git.kernel.org/bpf/bpf-next/c/5d2784e25d7a
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-09-02 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 21:07 [PATCH bpf-next] bpftool: Add missing blank lines in bpftool-net doc example Quentin Monnet
2024-09-02 16:30 ` 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=172529462950.3935899.5396247121344260485.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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