From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org,
kernel-team@cloudflare.com, yhs@fb.com
Subject: Re: [PATCH bpf-next v2 0/2] Split bpf_sk_lookup remote_port field
Date: Wed, 09 Feb 2022 19:50:08 +0000 [thread overview]
Message-ID: <164443620898.30796.17334556024163355601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220209184333.654927-1-jakub@cloudflare.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.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
prev parent reply other threads:[~2022-02-09 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 18:43 [PATCH bpf-next v2 0/2] Split bpf_sk_lookup remote_port field Jakub Sitnicki
2022-02-09 18:43 ` [PATCH bpf-next v2 1/2] bpf: Make remote_port field in struct bpf_sk_lookup 16-bit wide Jakub Sitnicki
2022-02-09 18:43 ` [PATCH bpf-next v2 2/2] selftests/bpf: Cover 4-byte load from remote_port in bpf_sk_lookup Jakub Sitnicki
2022-02-16 21:44 ` Andrii Nakryiko
2022-02-17 14:18 ` Ilya Leoshkevich
2022-02-17 16:11 ` Jakub Sitnicki
2022-02-19 14:37 ` Jakub Sitnicki
2022-02-21 18:34 ` Jakub Sitnicki
2022-02-09 19: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=164443620898.30796.17334556024163355601.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=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=netdev@vger.kernel.org \
--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 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.