BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: corbet@lwn.net, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
	yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
	brouer@redhat.com, linux-doc@vger.kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, lixuefeng@loongson.cn
Subject: Re: [PATCH bpf-next v3] bpf: Fix some invalid links in bpf_devel_QA.rst
Date: Thu, 22 Apr 2021 21:30:10 +0000	[thread overview]
Message-ID: <161912701005.19496.9540083866357841252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1619062560-30483-1-git-send-email-yangtiezhu@loongson.cn>

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Thu, 22 Apr 2021 11:36:00 +0800 you wrote:
> There exist some errors "404 Not Found" when I click the link
> of "MAINTAINERS" [1], "samples/bpf/" [2] and "selftests" [3]
> in the documentation "HOWTO interact with BPF subsystem" [4].
> 
> As Alexei Starovoitov suggested, just remove "MAINTAINERS" and
> "samples/bpf/" links and use correct link of "selftests".
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3] bpf: Fix some invalid links in bpf_devel_QA.rst
    https://git.kernel.org/bpf/bpf-next/c/64ef3ddfa95e

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-04-22 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  3:36 [PATCH bpf-next v3] bpf: Fix some invalid links in bpf_devel_QA.rst Tiezhu Yang
2021-04-22  9:15 ` Jesper Dangaard Brouer
2021-04-22 17:09   ` Jesper Dangaard Brouer
2021-04-22 21:30 ` 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=161912701005.19496.9540083866357841252.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yangtiezhu@loongson.cn \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox