From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
bpf@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/2] selftests: net: extract BPF building logic from the Makefile
Date: Tue, 23 Apr 2024 11:35:40 -0700 [thread overview]
Message-ID: <20240423183542.3807234-1-kuba@kernel.org> (raw)
This has been sitting in my tree for a while. I will soon add YNL/libynl
support for networking selftests. This prompted a small cleanup of
the selftest makefile for net/. We don't want to be piling logic
for each library in there. YNL will get its own .mk file which can
be included. Do the same for the BPF building section, already.
No funcional changes here, just a code move and small rename.
Jakub Kicinski (2):
selftests: net: name bpf objects consistently and simplify Makefile
selftests: net: extract BPF building logic from the Makefile
tools/testing/selftests/net/Makefile | 60 +------------------
tools/testing/selftests/net/bpf.mk | 53 ++++++++++++++++
.../net/{nat6to4.c => nat6to4.bpf.c} | 0
tools/testing/selftests/net/udpgro.sh | 2 +-
tools/testing/selftests/net/udpgro_bench.sh | 2 +-
tools/testing/selftests/net/udpgro_frglist.sh | 8 +--
tools/testing/selftests/net/udpgro_fwd.sh | 2 +-
tools/testing/selftests/net/veth.sh | 2 +-
.../net/{xdp_dummy.c => xdp_dummy.bpf.c} | 0
9 files changed, 64 insertions(+), 65 deletions(-)
create mode 100644 tools/testing/selftests/net/bpf.mk
rename tools/testing/selftests/net/{nat6to4.c => nat6to4.bpf.c} (100%)
rename tools/testing/selftests/net/{xdp_dummy.c => xdp_dummy.bpf.c} (100%)
--
2.44.0
next reply other threads:[~2024-04-23 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 18:35 Jakub Kicinski [this message]
2024-04-23 18:35 ` [PATCH net-next 1/2] selftests: net: name bpf objects consistently and simplify Makefile Jakub Kicinski
2024-04-23 18:35 ` [PATCH net-next 2/2] selftests: net: extract BPF building logic from the Makefile Jakub Kicinski
2024-04-25 3:50 ` [PATCH net-next 0/2] " patchwork-bot+netdevbpf
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=20240423183542.3807234-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).