public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
	song@kernel.org, kernel-team@meta.com, andrii@kernel.org,
	sdf@fomichev.me, geliang@kernel.org, sinquersw@gmail.com,
	kuifeng@meta.com
Subject: Re: [PATCH bpf-next v8 0/6] monitor network traffic for flaky test cases
Date: Thu, 15 Aug 2024 19:50:35 +0000	[thread overview]
Message-ID: <172375143529.2996010.3717574409082481079.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240815053254.470944-1-thinker.li@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Wed, 14 Aug 2024 22:32:48 -0700 you wrote:
> Capture packets in the background for flaky test cases related to
> network features.
> 
> We have some flaky test cases that are difficult to debug without
> knowing what the traffic looks like. Capturing packets, the CI log and
> packet files may help developers to fix these flaky test cases.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v8,1/6] selftests/bpf: Add traffic monitor functions.
    https://git.kernel.org/bpf/bpf-next/c/f52403b6bfea
  - [bpf-next,v8,2/6] selftests/bpf: Add the traffic monitor option to test_progs.
    https://git.kernel.org/bpf/bpf-next/c/f5281aacec85
  - [bpf-next,v8,3/6] selftests/bpf: netns_new() and netns_free() helpers.
    https://git.kernel.org/bpf/bpf-next/c/1e115a58be0f
  - [bpf-next,v8,4/6] selftests/bpf: Monitor traffic for tc_redirect.
    https://git.kernel.org/bpf/bpf-next/c/52a5b8a30fa8
  - [bpf-next,v8,5/6] selftests/bpf: Monitor traffic for sockmap_listen.
    https://git.kernel.org/bpf/bpf-next/c/b407b52b1850
  - [bpf-next,v8,6/6] selftests/bpf: Monitor traffic for select_reuseport.
    https://git.kernel.org/bpf/bpf-next/c/69354085975a

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-08-15 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  5:32 [PATCH bpf-next v8 0/6] monitor network traffic for flaky test cases Kui-Feng Lee
2024-08-15  5:32 ` [PATCH bpf-next v8 1/6] selftests/bpf: Add traffic monitor functions Kui-Feng Lee
2024-08-15  5:32 ` [PATCH bpf-next v8 2/6] selftests/bpf: Add the traffic monitor option to test_progs Kui-Feng Lee
2024-08-15  5:32 ` [PATCH bpf-next v8 3/6] selftests/bpf: netns_new() and netns_free() helpers Kui-Feng Lee
2024-08-15  5:32 ` [PATCH bpf-next v8 4/6] selftests/bpf: Monitor traffic for tc_redirect Kui-Feng Lee
2024-08-15  5:32 ` [PATCH bpf-next v8 5/6] selftests/bpf: Monitor traffic for sockmap_listen Kui-Feng Lee
2024-08-15  5:32 ` [PATCH bpf-next v8 6/6] selftests/bpf: Monitor traffic for select_reuseport Kui-Feng Lee
2024-08-15 17:00 ` [PATCH bpf-next v8 0/6] monitor network traffic for flaky test cases Kui-Feng Lee
2024-08-15 19: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=172375143529.2996010.3717574409082481079.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=geliang@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kuifeng@meta.com \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=sinquersw@gmail.com \
    --cc=song@kernel.org \
    --cc=thinker.li@gmail.com \
    /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