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, 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, void@manifault.com,
davem@davemloft.net, me@tobin.cc
Subject: Re: [PATCH bpf-next v2] bpf, docs: Use internal linking for link to netdev subsystem doc
Date: Fri, 17 Mar 2023 13:10:18 +0000 [thread overview]
Message-ID: <167905861818.22019.13807434741181931132.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230314074449.23620-1-bagasdotme@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 14 Mar 2023 14:44:49 +0700 you wrote:
> Commit d56b0c461d19da ("bpf, docs: Fix link to netdev-FAQ target")
> attempts to fix linking problem to undefined "netdev-FAQ" label
> introduced in 287f4fa99a5281 ("docs: Update references to netdev-FAQ")
> by changing internal cross reference to netdev subsystem documentation
> (Documentation/process/maintainer-netdev.rst) to external one at
> docs.kernel.org. However, the linking problem is still not
> resolved, as the generated link points to non-existent netdev-FAQ
> section of the external doc, which when clicked, will instead going to
> the top of the doc.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf, docs: Use internal linking for link to netdev subsystem doc
https://git.kernel.org/bpf/bpf-next/c/0f10f647f455
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:[~2023-03-17 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 7:44 [PATCH bpf-next v2] bpf, docs: Use internal linking for link to netdev subsystem doc Bagas Sanjaya
2023-03-17 13:10 ` 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=167905861818.22019.13807434741181931132.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=davem@davemloft.net \
--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=martin.lau@linux.dev \
--cc=me@tobin.cc \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=void@manifault.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.