BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadfed@meta.com>
Cc: vadim.fedorenko@linux.dev, daniel@iogearbox.net,
	andrii@kernel.org, ast@kernel.org, mykolal@fb.com,
	kuba@kernel.org, martin.lau@linux.dev, bpf@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 1/2] bpf: add CHECKSUM_COMPLETE to bpf test progs
Date: Thu, 13 Jun 2024 12:40:30 +0000	[thread overview]
Message-ID: <171828243073.30018.3001493447683443532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240606145851.229116-1-vadfed@meta.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Thu, 6 Jun 2024 07:58:50 -0700 you wrote:
> Add special flag to validate that TC BPF program properly updates
> checksum information in skb.
> 
> Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
> ---
> v3 -> v4:
>  - use network header offset as starting point for checksum
>  - use folded checksum values to compare results
> v2 -> v3:
>  - remove BIT() macro from uapi bpf.h
>  - change error code to EBADMSG
> v1 -> v2:
>  - clean unused variable
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/2] bpf: add CHECKSUM_COMPLETE to bpf test progs
    https://git.kernel.org/bpf/bpf-next/c/a3cfe84cca28
  - [bpf-next,v4,2/2] selftests: bpf: validate CHECKSUM_COMPLETE option
    https://git.kernel.org/bpf/bpf-next/c/041c1dc988fd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-13 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 14:58 [PATCH bpf-next v4 1/2] bpf: add CHECKSUM_COMPLETE to bpf test progs Vadim Fedorenko
2024-06-06 14:58 ` [PATCH bpf-next v4 2/2] selftests: bpf: validate CHECKSUM_COMPLETE option Vadim Fedorenko
2024-06-12 14:49 ` [PATCH bpf-next v4 1/2] bpf: add CHECKSUM_COMPLETE to bpf test progs Jakub Kicinski
2024-06-13 11:18   ` Vadim Fedorenko
2024-06-13 12:32     ` Daniel Borkmann
2024-06-13 12:40 ` 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=171828243073.30018.3001493447683443532.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=kuba@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=vadfed@meta.com \
    --cc=vadim.fedorenko@linux.dev \
    /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