From: patchwork-bot+netdevbpf@kernel.org
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: jackmanb@google.com, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, andrii@kernel.org, bjorn.topel@gmail.com,
netdev@vger.kernel.org, mchehab+huawei@kernel.org,
linux-doc@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for bpf-next] docs: bpf: add minimal markup to address doc warning
Date: Mon, 18 Jan 2021 23:10:07 +0000 [thread overview]
Message-ID: <161101140785.10967.10936414258257855749.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210118080004.6367-1-lukas.bulwahn@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Mon, 18 Jan 2021 09:00:04 +0100 you wrote:
> Commit 91c960b00566 ("bpf: Rename BPF_XADD and prepare to encode other
> atomics in .imm") modified the BPF documentation, but missed some ReST
> markup.
>
> Hence, make htmldocs warns on Documentation/networking/filter.rst:1053:
>
> WARNING: Inline emphasis start-string without end-string.
>
> [...]
Here is the summary with links:
- [for,bpf-next] docs: bpf: add minimal markup to address doc warning
https://git.kernel.org/bpf/bpf-next/c/95204c9bfa48
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-01-18 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 8:00 [PATCH for bpf-next] docs: bpf: add minimal markup to address doc warning Lukas Bulwahn
2021-01-18 10:46 ` Brendan Jackman
2021-01-18 23:10 ` 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=161101140785.10967.10936414258257855749.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jackmanb@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=netdev@vger.kernel.org \
/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).