Re: [PATCH bpf-next v3 0/2] docs: fix sphinx warnings for cpu+dev maps

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@xxxxxxxxxxxxx>:

On Wed, 23 Nov 2022 09:23:19 +0000 you wrote:
> From: Maryam Tahhan <mtahhan@xxxxxxxxxx>
> 
> 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





[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux