From: patchwork-bot+netdevbpf@kernel.org
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, corbet@lwn.net,
nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com,
dthaler@microsoft.com, lkp@intel.com
Subject: Re: [PATCH bpf-next] Documentation: bpf: Add implementation notes documentations to table of contents
Date: Mon, 03 Oct 2022 16:20:15 +0000 [thread overview]
Message-ID: <166481401546.8397.14038744797480125600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221002032022.24693-1-bagasdotme@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 2 Oct 2022 10:20:23 +0700 you wrote:
> Sphinx reported warnings on missing implementation notes documentations in the
> table of contents:
>
> Documentation/bpf/clang-notes.rst: WARNING: document isn't included in any toctree
> Documentation/bpf/linux-notes.rst: WARNING: document isn't included in any toctree
>
> Add these documentations to the table of contents (index.rst) of BPF
> documentation to fix the warnings.
>
> [...]
Here is the summary with links:
- [bpf-next] Documentation: bpf: Add implementation notes documentations to table of contents
https://git.kernel.org/bpf/bpf-next/c/736baae643cb
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:[~2022-10-03 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 3:20 [PATCH bpf-next] Documentation: bpf: Add implementation notes documentations to table of contents Bagas Sanjaya
2022-10-03 16:20 ` 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=166481401546.8397.14038744797480125600.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dthaler@microsoft.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=trix@redhat.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.