From: patchwork-bot+netdevbpf@kernel.org
To: Weqaar Janjua <weqaar.janjua@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
daniel@iogearbox.net, ast@kernel.org, yhs@fb.com,
magnus.karlsson@gmail.com, bjorn.topel@intel.com,
weqaar.a.janjua@intel.com, shuah@kernel.org,
skhan@linuxfoundation.org, linux-kselftest@vger.kernel.org,
anders.roxell@linaro.org, jonathan.lemon@gmail.com
Subject: Re: [PATCH bpf-next v4 0/5] selftests/bpf: xsk selftests
Date: Wed, 09 Dec 2020 16:00:07 +0000 [thread overview]
Message-ID: <160752960729.12976.12661383715171656742.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201207215333.11586-1-weqaar.a.janjua@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Mon, 7 Dec 2020 21:53:28 +0000 you wrote:
> This patch set adds AF_XDP selftests based on veth to selftests/bpf.
>
> # Topology:
> # ---------
> # -----------
> # _ | Process | _
> # / ----------- \
> # / | \
> # / | \
> # ----------- | -----------
> # | Thread1 | | | Thread2 |
> # ----------- | -----------
> # | | |
> # ----------- | -----------
> # | xskX | | | xskY |
> # ----------- | -----------
> # | | |
> # ----------- | ----------
> # | vethX | --------- | vethY |
> # ----------- peer ----------
> # | | |
> # namespaceX | namespaceY
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/5] selftests/bpf: xsk selftests framework
https://git.kernel.org/bpf/bpf-next/c/a89052572ebb
- [bpf-next,v4,2/5] selftests/bpf: xsk selftests - SKB POLL, NOPOLL
https://git.kernel.org/bpf/bpf-next/c/facb7cb2e909
- [bpf-next,v4,3/5] selftests/bpf: xsk selftests - DRV POLL, NOPOLL
https://git.kernel.org/bpf/bpf-next/c/9103a8594d93
- [bpf-next,v4,4/5] selftests/bpf: xsk selftests - Socket Teardown - SKB, DRV
https://git.kernel.org/bpf/bpf-next/c/6674bf66560a
- [bpf-next,v4,5/5] selftests/bpf: xsk selftests - Bi-directional Sockets - SKB, DRV
https://git.kernel.org/bpf/bpf-next/c/7d20441eb05e
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:[~2020-12-09 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 21:53 [PATCH bpf-next v4 0/5] selftests/bpf: xsk selftests Weqaar Janjua
2020-12-07 21:53 ` [PATCH bpf-next v4 1/5] selftests/bpf: xsk selftests framework Weqaar Janjua
2020-12-07 21:53 ` [PATCH bpf-next v4 2/5] selftests/bpf: xsk selftests - SKB POLL, NOPOLL Weqaar Janjua
2020-12-09 18:29 ` Yonghong Song
2020-12-10 11:55 ` Weqaar Janjua
2020-12-07 21:53 ` [PATCH bpf-next v4 3/5] selftests/bpf: xsk selftests - DRV " Weqaar Janjua
2020-12-07 21:53 ` [PATCH bpf-next v4 4/5] selftests/bpf: xsk selftests - Socket Teardown - SKB, DRV Weqaar Janjua
2020-12-07 21:53 ` [PATCH bpf-next v4 5/5] selftests/bpf: xsk selftests - Bi-directional Sockets " Weqaar Janjua
2020-12-08 3:56 ` [PATCH bpf-next v4 0/5] selftests/bpf: xsk selftests Yonghong Song
2020-12-08 7:03 ` Björn Töpel
2020-12-09 16:00 ` 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=160752960729.12976.12661383715171656742.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jonathan.lemon@gmail.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=magnus.karlsson@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=weqaar.a.janjua@intel.com \
--cc=weqaar.janjua@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox