From: patchwork-bot+netdevbpf@kernel.org
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH bpf-next] docs: bpf: Fix literal block
Date: Tue, 27 Apr 2021 15:40:08 +0000 [thread overview]
Message-ID: <161953800853.25842.5867813619345155071.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210424021208.832116-1-hengqi.chen@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Sat, 24 Apr 2021 10:12:08 +0800 you wrote:
> Add a missing colon so that the code block followed can be rendered
> properly.
>
> Signed-off-by: Hengqi Chen <hengqi.chen@gmail.com>
> ---
> Documentation/networking/filter.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [bpf-next] docs: bpf: Fix literal block
https://git.kernel.org/bpf/bpf-next/c/2551c2d19c04
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-04-27 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 2:12 [PATCH bpf-next] docs: bpf: Fix literal block Hengqi Chen
2021-04-27 15: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=161953800853.25842.5867813619345155071.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hengqi.chen@gmail.com \
--cc=linux-doc@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).