[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <164443620898.30796.17334556024163355601.git-patchwork-notify@kernel.org>
Date: Wed, 09 Feb 2022 19:50:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Sitnicki <jakub@...udflare.com>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org,
kernel-team@...udflare.com, yhs@...com
Subject: Re: [PATCH bpf-next v2 0/2] Split bpf_sk_lookup remote_port field
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Wed, 9 Feb 2022 19:43:31 +0100 you wrote:
> Following the recent split-up of the bpf_sock dst_port field, apply the same to
> technique to the bpf_sk_lookup remote_port field to make uAPI more user
> friendly.
>
> v1 -> v2:
> - Remove remote_port range check and cast to be16 in TEST_RUN for sk_lookup
> (kernel test robot)
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Make remote_port field in struct bpf_sk_lookup 16-bit wide
https://git.kernel.org/bpf/bpf-next/c/9a69e2b385f4
- [bpf-next,v2,2/2] selftests/bpf: Cover 4-byte load from remote_port in bpf_sk_lookup
https://git.kernel.org/bpf/bpf-next/c/2ed0dc5937d3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists