From: patchwork-bot+netdevbpf@kernel.org
To: Bastien Curutchet (eBPF Foundation) <bastien.curutchet@bootlin.com>
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@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
thomas.petazzoni@bootlin.com, alexis.lothore@bootlin.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Remove with_addr.sh and with_tunnels.sh
Date: Sat, 08 Feb 2025 02:40:30 +0000 [thread overview]
Message-ID: <173898243078.2462994.9706001313685951312.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250204-with-v1-1-387a42118cd4@bootlin.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Tue, 04 Feb 2025 11:59:43 +0100 you wrote:
> Those two scripts were used by test_flow_dissector.sh to setup/cleanup
> the network topology before/after the tests. test_flow_dissector.sh
> have been deleted by commit 63b37657c5fd ("selftests/bpf: remove
> test_flow_dissector.sh") so they aren't used anywhere now.
>
> Remove the two unused scripts and their Makefile entries.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Remove with_addr.sh and with_tunnels.sh
https://git.kernel.org/bpf/bpf-next/c/9b6cdaf2ac85
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:[~2025-02-08 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 10:59 [PATCH bpf-next] selftests/bpf: Remove with_addr.sh and with_tunnels.sh Bastien Curutchet (eBPF Foundation)
2025-02-08 2: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=173898243078.2462994.9706001313685951312.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--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