From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/5] bpf: Follow up on bpf __sk_buff->tstamp
Date: Thu, 10 Mar 2022 22:00:11 +0000 [thread overview]
Message-ID: <164694961150.7517.4845832258567131034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220309090444.3710464-1-kafai@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 9 Mar 2022 01:04:44 -0800 you wrote:
> This set is a follow up on the bpf side based on discussion [0].
>
> Patch 1 is to remove some skbuff macros that are used in bpf filter.c
>
> Patch 2 and 3 are to simplify the bpf insn rewrite on __sk_buff->tstamp.
>
> Patch 4 is to simplify the bpf uapi by modeling the __sk_buff->tstamp
> and __sk_buff->tstamp_type (was delivery_time_type) the same as its kernel
> counter part skb->tstamp and skb->mono_delivery_time.
>
> [...]
Here is the summary with links:
- [bpf-next,1/5] bpf: net: Remove TC_AT_INGRESS_OFFSET and SKB_MONO_DELIVERY_TIME_OFFSET macro
https://git.kernel.org/bpf/bpf-next/c/3b5d4ddf8fe1
- [bpf-next,2/5] bpf: Simplify insn rewrite on BPF_READ __sk_buff->tstamp
https://git.kernel.org/bpf/bpf-next/c/539de9328e3a
- [bpf-next,3/5] bpf: Simplify insn rewrite on BPF_WRITE __sk_buff->tstamp
https://git.kernel.org/bpf/bpf-next/c/9d90db97e4d4
- [bpf-next,4/5] bpf: Remove BPF_SKB_DELIVERY_TIME_NONE and rename s/delivery_time_/tstamp_/
https://git.kernel.org/bpf/bpf-next/c/9bb984f28d5b
- [bpf-next,5/5] bpf: selftests: Update tests after s/delivery_time/tstamp/ change in bpf.h
https://git.kernel.org/bpf/bpf-next/c/3daf0896f3f9
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-03-10 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 9:04 [PATCH bpf-next 0/5] bpf: Follow up on bpf __sk_buff->tstamp Martin KaFai Lau
2022-03-09 9:04 ` [PATCH bpf-next 1/5] bpf: net: Remove TC_AT_INGRESS_OFFSET and SKB_MONO_DELIVERY_TIME_OFFSET macro Martin KaFai Lau
2022-03-09 9:04 ` [PATCH bpf-next 2/5] bpf: Simplify insn rewrite on BPF_READ __sk_buff->tstamp Martin KaFai Lau
2022-03-09 9:05 ` [PATCH bpf-next 3/5] bpf: Simplify insn rewrite on BPF_WRITE __sk_buff->tstamp Martin KaFai Lau
2022-03-09 9:05 ` [PATCH bpf-next 4/5] bpf: Remove BPF_SKB_DELIVERY_TIME_NONE and rename s/delivery_time_/tstamp_/ Martin KaFai Lau
2022-03-09 9:05 ` [PATCH bpf-next 5/5] bpf: selftests: Update tests after s/delivery_time/tstamp/ change in bpf.h Martin KaFai Lau
2022-03-10 22:00 ` 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=164694961150.7517.4845832258567131034.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=kafai@fb.com \
--cc=kernel-team@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;
as well as URLs for NNTP newsgroup(s).