From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, kuniyu@amazon.com
Subject: Re: [PATCH bpf-next 0/1] selftests/bpf: reduce tcp_custom_syncookie verification complexity
Date: Thu, 22 Feb 2024 16:50:28 +0000 [thread overview]
Message-ID: <170862062815.30322.2285512260477496828.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240222150300.14909-1-eddyz87@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 22 Feb 2024 17:02:59 +0200 you wrote:
> Thread [0] discusses a fix for bpf_loop() handling bug.
> That change makes tcp_custom_syncookie test too complex to verify.
> The fix discussed in [0] would be sent via 'bpf' tree,
> tcp_custom_syncookie test is not in 'bpf' tree yet.
> As agreed in [0] I'm sending syncookie test update separately.
>
> [0] https://lore.kernel.org/bpf/20240216150334.31937-1-eddyz87@gmail.com/
>
> [...]
Here is the summary with links:
- [bpf-next,1/1] selftests/bpf: update tcp_custom_syncookie to use scalar packet offset
https://git.kernel.org/bpf/bpf-next/c/b546b5752695
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:[~2024-02-22 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 15:02 [PATCH bpf-next 0/1] selftests/bpf: reduce tcp_custom_syncookie verification complexity Eduard Zingerman
2024-02-22 15:03 ` [PATCH bpf-next 1/1] selftests/bpf: update tcp_custom_syncookie to use scalar packet offset Eduard Zingerman
2024-02-22 16: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=170862062815.30322.2285512260477496828.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=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=kuniyu@amazon.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@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 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.