From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, kernel-team@fb.com,
pabeni@redhat.com
Subject: Re: [PATCH v2 bpf-next 00/17] bpf: net: Remove duplicated code from bpf_getsockopt()
Date: Sat, 03 Sep 2022 03:50:19 +0000 [thread overview]
Message-ID: <166217701936.16352.10281500162790893698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220902002750.2887415-1-kafai@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 1 Sep 2022 17:27:50 -0700 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> The earlier commits [0] removed duplicated code from bpf_setsockopt().
> This series is to remove duplicated code from bpf_getsockopt().
>
> Unlike the setsockopt() which had already changed to take
> the sockptr_t argument, the same has not been done to
> getsockopt(). This is the extra step being done in this
> series.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,01/17] net: Change sock_getsockopt() to take the sk ptr instead of the sock ptr
https://git.kernel.org/bpf/bpf-next/c/ba74a7608dc1
- [v2,bpf-next,02/17] bpf: net: Change sk_getsockopt() to take the sockptr_t argument
https://git.kernel.org/bpf/bpf-next/c/4ff09db1b79b
- [v2,bpf-next,03/17] bpf: net: Avoid sk_getsockopt() taking sk lock when called from bpf
https://git.kernel.org/bpf/bpf-next/c/2c5b6bf5cda0
- [v2,bpf-next,04/17] bpf: net: Change do_tcp_getsockopt() to take the sockptr_t argument
https://git.kernel.org/bpf/bpf-next/c/34704ef024ae
- [v2,bpf-next,05/17] bpf: net: Avoid do_tcp_getsockopt() taking sk lock when called from bpf
https://git.kernel.org/bpf/bpf-next/c/d51bbff2aba7
- [v2,bpf-next,06/17] bpf: net: Change do_ip_getsockopt() to take the sockptr_t argument
https://git.kernel.org/bpf/bpf-next/c/728f064cd7eb
- [v2,bpf-next,07/17] bpf: net: Avoid do_ip_getsockopt() taking sk lock when called from bpf
https://git.kernel.org/bpf/bpf-next/c/1985320c54dd
- [v2,bpf-next,08/17] net: Remove unused flags argument from do_ipv6_getsockopt
https://git.kernel.org/bpf/bpf-next/c/75f23979888a
- [v2,bpf-next,09/17] net: Add a len argument to compat_ipv6_get_msfilter()
https://git.kernel.org/bpf/bpf-next/c/9c3f9707decd
- [v2,bpf-next,10/17] bpf: net: Change do_ipv6_getsockopt() to take the sockptr_t argument
https://git.kernel.org/bpf/bpf-next/c/6dadbe4bac68
- [v2,bpf-next,11/17] bpf: net: Avoid do_ipv6_getsockopt() taking sk lock when called from bpf
https://git.kernel.org/bpf/bpf-next/c/0f95f7d42611
- [v2,bpf-next,12/17] bpf: Embed kernel CONFIG check into the if statement in bpf_getsockopt
https://git.kernel.org/bpf/bpf-next/c/c2b063ca3458
- [v2,bpf-next,13/17] bpf: Change bpf_getsockopt(SOL_SOCKET) to reuse sk_getsockopt()
https://git.kernel.org/bpf/bpf-next/c/65ddc82d3b96
- [v2,bpf-next,14/17] bpf: Change bpf_getsockopt(SOL_TCP) to reuse do_tcp_getsockopt()
https://git.kernel.org/bpf/bpf-next/c/273b7f0fb448
- [v2,bpf-next,15/17] bpf: Change bpf_getsockopt(SOL_IP) to reuse do_ip_getsockopt()
https://git.kernel.org/bpf/bpf-next/c/fd969f25fe24
- [v2,bpf-next,16/17] bpf: Change bpf_getsockopt(SOL_IPV6) to reuse do_ipv6_getsockopt()
https://git.kernel.org/bpf/bpf-next/c/38566ec06f52
- [v2,bpf-next,17/17] selftest/bpf: Add test for bpf_getsockopt()
https://git.kernel.org/bpf/bpf-next/c/f649f992deee
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-09-03 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 0:27 [PATCH v2 bpf-next 00/17] bpf: net: Remove duplicated code from bpf_getsockopt() Martin KaFai Lau
2022-09-02 22:16 ` sdf
2022-09-03 3: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=166217701936.16352.10281500162790893698.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=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).