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, imagedong@tencent.com,
kafai@fb.com
Subject: Re: [PATCH bpf-next v2 0/2] Split bpf_sock dst_port field
Date: Mon, 31 Jan 2022 20:53:42 +0000 [thread overview]
Message-ID: <164366242265.17453.14979978699179482148.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220130115518.213259-1-jakub@cloudflare.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 30 Jan 2022 12:55:16 +0100 you wrote:
> This is a follow-up to discussion around the idea of making dst_port in struct
> bpf_sock a 16-bit field that happened in [1].
>
> v2:
> - use an anonymous field for zero padding (Alexei)
>
> v1:
> - keep dst_field offset unchanged to prevent existing BPF program breakage
> (Martin)
> - allow 8-bit loads from dst_port[0] and [1]
> - add test coverage for the verifier and the context access converter
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Make dst_port field in struct bpf_sock 16-bit wide
https://git.kernel.org/bpf/bpf-next/c/4421a582718a
- [bpf-next,v2,2/2] selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
https://git.kernel.org/bpf/bpf-next/c/8f50f16ff39d
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-01-31 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 11:55 [PATCH bpf-next v2 0/2] Split bpf_sock dst_port field Jakub Sitnicki
2022-01-30 11:55 ` [PATCH bpf-next v2 1/2] bpf: Make dst_port field in struct bpf_sock 16-bit wide Jakub Sitnicki
2022-01-30 11:55 ` [PATCH bpf-next v2 2/2] selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads Jakub Sitnicki
2022-01-31 20:14 ` [PATCH bpf-next v2 0/2] Split bpf_sock dst_port field Martin KaFai Lau
2022-01-31 20:53 ` 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=164366242265.17453.14979978699179482148.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=imagedong@tencent.com \
--cc=jakub@cloudflare.com \
--cc=kafai@fb.com \
--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