From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, geliang.tang@suse.com,
mptcp@lists.linux.dev
Subject: Re: [PATCH bpf-next v5 0/7] bpf: mptcp: Support for mptcp_sock
Date: Fri, 20 May 2022 22:50:13 +0000 [thread overview]
Message-ID: <165308701349.8703.10845303624586414440.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220519233016.105670-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 19 May 2022 16:30:09 -0700 you wrote:
> This patch set adds BPF access to mptcp_sock structures, along with
> associated self tests. You may recognize some of the code from earlier
> (https://lore.kernel.org/bpf/20200918121046.190240-6-nicolas.rybowski@tessares.net/)
> but it has been reworked quite a bit.
>
>
> v1 -> v2: Emit BTF type, add func_id checks in verifier.c and bpf_trace.c,
> remove build check for CONFIG_BPF_JIT, add selftest check for CONFIG_MPTCP,
> and add a patch to include CONFIG_IKCONFIG/CONFIG_IKCONFIG_PROC for the
> BPF self tests.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/7] bpf: add bpf_skc_to_mptcp_sock_proto
https://git.kernel.org/bpf/bpf-next/c/3bc253c2e652
- [bpf-next,v5,2/7] selftests/bpf: Enable CONFIG_IKCONFIG_PROC in config
https://git.kernel.org/bpf/bpf-next/c/d3294cb1e06d
- [bpf-next,v5,3/7] selftests/bpf: add MPTCP test base
https://git.kernel.org/bpf/bpf-next/c/8039d353217c
- [bpf-next,v5,4/7] selftests/bpf: test bpf_skc_to_mptcp_sock
https://git.kernel.org/bpf/bpf-next/c/3bc48b56e345
- [bpf-next,v5,5/7] selftests/bpf: verify token of struct mptcp_sock
https://git.kernel.org/bpf/bpf-next/c/026622346772
- [bpf-next,v5,6/7] selftests/bpf: verify ca_name of struct mptcp_sock
https://git.kernel.org/bpf/bpf-next/c/ccc090f46900
- [bpf-next,v5,7/7] selftests/bpf: verify first of struct mptcp_sock
https://git.kernel.org/bpf/bpf-next/c/4f90d034bba9
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:[~2022-05-20 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 23:30 [PATCH bpf-next v5 0/7] bpf: mptcp: Support for mptcp_sock Mat Martineau
2022-05-19 23:30 ` [PATCH bpf-next v5 1/7] bpf: add bpf_skc_to_mptcp_sock_proto Mat Martineau
2022-05-19 23:30 ` [PATCH bpf-next v5 2/7] selftests/bpf: Enable CONFIG_IKCONFIG_PROC in config Mat Martineau
2022-05-19 23:30 ` [PATCH bpf-next v5 3/7] selftests/bpf: add MPTCP test base Mat Martineau
2022-05-19 23:30 ` [PATCH bpf-next v5 4/7] selftests/bpf: test bpf_skc_to_mptcp_sock Mat Martineau
2022-05-19 23:30 ` [PATCH bpf-next v5 5/7] selftests/bpf: verify token of struct mptcp_sock Mat Martineau
2022-05-19 23:30 ` [PATCH bpf-next v5 6/7] selftests/bpf: verify ca_name " Mat Martineau
2022-05-19 23:30 ` [PATCH bpf-next v5 7/7] selftests/bpf: verify first " Mat Martineau
2022-05-20 22:46 ` [PATCH bpf-next v5 0/7] bpf: mptcp: Support for mptcp_sock Andrii Nakryiko
2022-05-21 0:01 ` Mat Martineau
2022-05-20 22:50 ` 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=165308701349.8703.10845303624586414440.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=mathew.j.martineau@linux.intel.com \
--cc=mptcp@lists.linux.dev \
--cc=netdev@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).