From: patchwork-bot+netdevbpf@kernel.org
To: Geliang Tang <geliang.tang@suse.com>
Cc: andrii@kernel.org, mykolal@fb.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] cleanups for sockmap_listen
Date: Fri, 06 Oct 2023 05:10:29 +0000 [thread overview]
Message-ID: <169656902911.30880.9997812914153027889.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1696490003.git.geliang.tang@suse.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 5 Oct 2023 15:21:50 +0800 you wrote:
> v2:
> - rename c0/c1 to cli0/cli1, p0/p1 to peer0/perr1 as Daniel suggested.
>
> Two cleanups for sockmap_listen selftests: enable a kconfig and add a
> new helper.
>
> Geliang Tang (2):
> selftests/bpf: Enable CONFIG_VSOCKETS in config
> selftests/bpf: Add pairs_redir_to_connected helper
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] selftests/bpf: Enable CONFIG_VSOCKETS in config
https://git.kernel.org/bpf/bpf-next/c/d549854bc58f
- [bpf-next,v2,2/2] selftests/bpf: Add pairs_redir_to_connected helper
(no matching commit)
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-10-06 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 7:21 [PATCH bpf-next v2 0/2] cleanups for sockmap_listen Geliang Tang
2023-10-05 7:21 ` [PATCH bpf-next v2 1/2] selftests/bpf: Enable CONFIG_VSOCKETS in config Geliang Tang
2023-10-05 7:21 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add pairs_redir_to_connected helper Geliang Tang
2023-10-06 5:18 ` Martin KaFai Lau
2023-10-13 10:40 ` Jakub Sitnicki
2023-10-06 5: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=169656902911.30880.9997812914153027889.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=daniel@iogearbox.net \
--cc=geliang.tang@suse.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.