bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrei Matei <andreimatei1@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/2] selftest/bpf: fix link in readme
Date: Tue, 24 Nov 2020 22:10:05 +0000	[thread overview]
Message-ID: <160625580579.16430.4916381760822076885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201122022205.57229-1-andreimatei1@gmail.com>

Hello:

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

On Sat, 21 Nov 2020 21:22:04 -0500 you wrote:
> The link was bad because of invalid rst; it was pointing to itself and
> was rendering badly.
> 
> Signed-off-by: Andrei Matei <andreimatei1@gmail.com>
> ---
>  tools/testing/selftests/bpf/README.rst | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)

Here is the summary with links:
  - [bpf-next,1/2] selftest/bpf: fix link in readme
    https://git.kernel.org/bpf/bpf-next/c/05a98d767273
  - [bpf-next,2/2] selftest/bpf: fix rst formatting in readme
    https://git.kernel.org/bpf/bpf-next/c/1c26ac6ab3ce

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



      parent reply	other threads:[~2020-11-24 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22  2:22 [PATCH bpf-next 1/2] selftest/bpf: fix link in readme Andrei Matei
2020-11-22  2:22 ` [PATCH bpf-next 2/2] selftest/bpf: fix rst formatting " Andrei Matei
2020-11-23  7:22   ` Yonghong Song
2020-11-24 18:29     ` Andrei Matei
2020-11-24 19:09       ` Yonghong Song
2020-11-24 19:11   ` Yonghong Song
2020-11-24 19:10 ` [PATCH bpf-next 1/2] selftest/bpf: fix link " Yonghong Song
2020-11-24 22: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=160625580579.16430.4916381760822076885.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andreimatei1@gmail.com \
    --cc=bpf@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).