From: Akira Yokosawa <akiyks@gmail.com>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Akira Yokosawa <akiyks@gmail.com>,
bpf@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH bpf-next v1] docs/bpf: Fix sphinx warnings in BPF map docs
Date: Wed, 23 Nov 2022 11:41:05 +0900 [thread overview]
Message-ID: <d9640d74-a353-73cf-d51c-81d9cfb1606b@gmail.com> (raw)
In-Reply-To: <20221122143933.91321-1-donald.hunter@gmail.com>
Hi Donald,
On Tue, 22 Nov 2022 14:39:33 +0000, Donald Hunter wrote:
> Fix duplicate C declaration warnings when using sphinx >= 3.1
>
> Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
> Reported-by: Akira Yokosawa <akiyks@gmail.com>
> Link: https://lore.kernel.org/bpf/ed4dac84-1b12-5c58-e4de-93ab9ac67c09@gmail.com
> ---
> Documentation/bpf/map_array.rst | 20 ++++++++++++---
> Documentation/bpf/map_hash.rst | 33 ++++++++++++++++++++----
> Documentation/bpf/map_lpm_trie.rst | 24 +++++++++++++++---
> Documentation/bpf/map_of_maps.rst | 6 ++++-
> Documentation/bpf/map_queue_stack.rst | 36 ++++++++++++++++++++++-----
> 5 files changed, 99 insertions(+), 20 deletions(-)
Thank you for taking care of them!
Reviewed-by: Akira Yokosawa <akiyks@gmail.com> # Sphinx >= 3.1
next prev parent reply other threads:[~2022-11-23 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 14:39 [PATCH bpf-next v1] docs/bpf: Fix sphinx warnings in BPF map docs Donald Hunter
2022-11-23 2:41 ` Akira Yokosawa [this message]
2022-11-24 0:10 ` patchwork-bot+netdevbpf
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=d9640d74-a353-73cf-d51c-81d9cfb1606b@gmail.com \
--to=akiyks@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=donald.hunter@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