Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Geliang Tang <geliang@kernel.org>
Cc: andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
	ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
	haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
	tanggeliang@kylinos.cn, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/5] use network helpers, part 6
Date: Thu, 06 Jun 2024 21:20:31 +0000	[thread overview]
Message-ID: <171770883171.30834.12991741087625316863.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1717054461.git.tanggeliang@kylinos.cn>

Hello:

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

On Thu, 30 May 2024 15:41:07 +0800 you wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> For moving dctcp test dedicated code out of do_test() into test_dctcp().
> This patchset adds a new helper start_test() in bpf_tcp_ca.c to refactor
> do_test().
> 
> Address Martin's comments for the previous series.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/5] selftests/bpf: Use connect_to_fd_opts in do_test in bpf_tcp_ca
    https://git.kernel.org/bpf/bpf-next/c/9abdfd8a2123
  - [bpf-next,2/5] selftests/bpf: Add start_test helper in bpf_tcp_ca
    https://git.kernel.org/bpf/bpf-next/c/fee97d0c9a14
  - [bpf-next,3/5] selftests/bpf: Use start_test in test_dctcp_fallback in bpf_tcp_ca
    https://git.kernel.org/bpf/bpf-next/c/224eeb5598c3
  - [bpf-next,4/5] selftests/bpf: Use start_test in test_dctcp in bpf_tcp_ca
    https://git.kernel.org/bpf/bpf-next/c/cd984b2ed624
  - [bpf-next,5/5] selftests/bpf: Drop useless arguments of do_test in bpf_tcp_ca
    https://git.kernel.org/bpf/bpf-next/c/f85af9d955ac

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-06 21:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30  7:41 [PATCH bpf-next 0/5] use network helpers, part 6 Geliang Tang
2024-05-30  7:41 ` [PATCH bpf-next 1/5] selftests/bpf: Use connect_to_fd_opts in do_test in bpf_tcp_ca Geliang Tang
2024-05-30  7:41 ` [PATCH bpf-next 2/5] selftests/bpf: Add start_test helper " Geliang Tang
2024-05-30  7:41 ` [PATCH bpf-next 3/5] selftests/bpf: Use start_test in test_dctcp_fallback " Geliang Tang
2024-05-30  7:41 ` [PATCH bpf-next 4/5] selftests/bpf: Use start_test in test_dctcp " Geliang Tang
2024-05-30  7:41 ` [PATCH bpf-next 5/5] selftests/bpf: Drop useless arguments of do_test " Geliang Tang
2024-06-06 21:20 ` 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=171770883171.30834.12991741087625316863.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=geliang@kernel.org \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=sdf@google.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tanggeliang@kylinos.cn \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox