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@google.com, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org,
rameezrehman408@hotmail.com
Subject: Re: [PATCH bpf-next 0/3] bpftool: Clean up indentation and formatting in docs
Date: Tue, 02 Apr 2024 14:00:33 +0000 [thread overview]
Message-ID: <171206643326.31786.8261961089605909281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240331200346.29118-1-qmo@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 31 Mar 2024 21:03:43 +0100 you wrote:
> The rST manual pages for bpftool would use a mix of tabs and spaces for
> indentation. While this is the norm in C code, this is rather unusual
> for rST documents, and over time we've seen many contributors use wrong
> levels of indentation for documentation update. This series simplifies
> the indentation in the rST files by removing some unnecessary levels of
> indent, and by using spaces only for what remains.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpftool: Use simpler indentation in source rST for documentation
https://git.kernel.org/bpf/bpf-next/c/f7b685436421
- [bpf-next,2/3] bpftool: Remove useless emphasis on command description in man pages
https://git.kernel.org/bpf/bpf-next/c/ea379b3ccc2e
- [bpf-next,3/3] bpftool: Clean-up typos, punctuation, list formatting in docs
https://git.kernel.org/bpf/bpf-next/c/a70f5d840a56
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-04-02 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 20:03 [PATCH bpf-next 0/3] bpftool: Clean up indentation and formatting in docs Quentin Monnet
2024-03-31 20:03 ` [PATCH bpf-next 1/3] bpftool: Use simpler indentation in source rST for documentation Quentin Monnet
2024-03-31 20:03 ` [PATCH bpf-next 2/3] bpftool: Remove useless emphasis on command description in man pages Quentin Monnet
2024-03-31 20:03 ` [PATCH bpf-next 3/3] bpftool: Clean-up typos, punctuation, list formatting in docs Quentin Monnet
2024-04-02 14: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=171206643326.31786.8261961089605909281.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=rameezrehman408@hotmail.com \
--cc=sdf@google.com \
--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