From: patchwork-bot+netdevbpf@kernel.org
To: Maryam Tahhan <mtahhan@redhat.com>
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
jbrouer@redhat.com, thoiland@redhat.com, donhunte@redhat.com,
akiyks@gmail.com
Subject: Re: [PATCH bpf-next v3 0/2] docs: fix sphinx warnings for cpu+dev maps
Date: Wed, 23 Nov 2022 21:40:16 +0000 [thread overview]
Message-ID: <166923961649.12268.10118409428649323814.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123092321.88558-1-mtahhan@redhat.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 23 Nov 2022 09:23:19 +0000 you wrote:
> From: Maryam Tahhan <mtahhan@redhat.com>
>
> Sphinx version >=3.1 warns about duplicate function declarations in the
> CPUMAP and DEVMAP documentation. This is because the function name is the
> same for Kernel and User space BPF progs but the parameters and return types
> they take is what differs. This patch moves from using the ``c:function::``
> directive to using the ``code-block:: c`` directive. The patches also fix
> the indentation for the text associated with the "new" code block delcarations.
> The missing support of c:namespace-push:: and c:namespace-pop:: directives by
> helper scripts for kernel documentation prevents using the ``c:function::``
> directive with proper namespacing.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] docs: fix sphinx warnings for cpumap
https://git.kernel.org/bpf/bpf-next/c/3685b0dc0d02
- [bpf-next,v3,2/2] docs: fix sphinx warnings for devmap
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-11-23 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 9:23 [PATCH bpf-next v3 0/2] docs: fix sphinx warnings for cpu+dev maps mtahhan
2022-11-23 9:23 ` [PATCH bpf-next v3 1/2] docs: fix sphinx warnings for cpumap mtahhan
2022-11-23 9:23 ` [PATCH bpf-next v3 2/2] docs: fix sphinx warnings for devmap mtahhan
2022-11-23 21:40 ` patchwork-bot+netdevbpf [this message]
2022-11-23 21:50 ` [PATCH bpf-next v3 0/2] docs: fix sphinx warnings for cpu+dev maps 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=166923961649.12268.10118409428649323814.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyks@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=donhunte@redhat.com \
--cc=jbrouer@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=mtahhan@redhat.com \
--cc=thoiland@redhat.com \
/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