From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Alexis_Lothor=C3=A9_=28eBPF_Foundation=29_=3Calexis=2Elothore=40bo?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
=?utf-8?q?otlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, memxor@gmail.com,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
shuah@kernel.org, davem@davemloft.net, kuba@kernel.org,
hawk@kernel.org, john.fastabend@gmail.com, sdf@fomichev.me,
ebpf@linuxfoundation.org, bastien.curutchet@bootlin.com,
thomas.petazzoni@bootlin.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, alan.maguire@oracle.com
Subject: Re: [PATCH bpf-next v2 0/2] selftests/bpf: drop xdping tool
Date: Fri, 24 Apr 2026 18:20:08 +0000 [thread overview]
Message-ID: <177705480880.1650547.11751423238740714723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260422-xdping-v2-0-c0f8ccedcf91@bootlin.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 22 Apr 2026 18:20:23 +0200 you wrote:
> Hello,
>
> this is the v2 of the small series dropping xdping tool. This removal is
> part of the larger effort aiming to tidy the bpf selftests directory.
> This new revision updates btf_dump test to make it use another bpf
> program rather than xdping_kern so that we can drop it as well.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] selftests/bpf: make btf_dump use xdp_dummy rather than xdping_kern
https://git.kernel.org/bpf/bpf-next/c/d4a2eeb2ac78
- [bpf-next,v2,2/2] selftests/bpf: drop xdping tool
https://git.kernel.org/bpf/bpf-next/c/feb13b19f3fa
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:[~2026-04-24 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 16:20 [PATCH bpf-next v2 0/2] selftests/bpf: drop xdping tool Alexis Lothoré (eBPF Foundation)
2026-04-22 16:20 ` [PATCH bpf-next v2 1/2] selftests/bpf: make btf_dump use xdp_dummy rather than xdping_kern Alexis Lothoré (eBPF Foundation)
2026-04-22 21:51 ` Paul Chaignon
2026-04-22 16:20 ` [PATCH bpf-next v2 2/2] selftests/bpf: drop xdping tool Alexis Lothoré (eBPF Foundation)
2026-04-22 21:53 ` Paul Chaignon
2026-04-24 18: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=177705480880.1650547.11751423238740714723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Alexis_Lothor=C3=A9_=28eBPF_Foundation=29_=3Calexis=2Elothore=40bo?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc==?utf-8?q?otlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ebpf@linuxfoundation.org \
--cc=eddyz87@gmail.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--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