From: Wang Yufen <wangyufen@huawei.com>
To: <netdev@vger.kernel.org>
Cc: <bpf@vger.kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<lina.wang@mediatek.com>, <deso@posteo.net>
Subject: [net 0/2] some fixes for selftest/net
Date: Tue, 11 Oct 2022 17:57:45 +0800 [thread overview]
Message-ID: <1665482267-30706-1-git-send-email-wangyufen@huawei.com> (raw)
Wang Yufen (2):
selftests/net: fix opening object file failed
selftests/net: fix missing xdp_dummy
tools/testing/selftests/bpf/progs/nat6to4.c | 285 ++++++++++++++++++++++++++
tools/testing/selftests/net/Makefile | 2 -
tools/testing/selftests/net/bpf/Makefile | 14 --
tools/testing/selftests/net/bpf/nat6to4.c | 285 --------------------------
tools/testing/selftests/net/udpgro.sh | 4 +-
tools/testing/selftests/net/udpgro_bench.sh | 4 +-
tools/testing/selftests/net/udpgro_frglist.sh | 12 +-
tools/testing/selftests/net/udpgro_fwd.sh | 2 +-
tools/testing/selftests/net/veth.sh | 8 +-
9 files changed, 300 insertions(+), 316 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/nat6to4.c
delete mode 100644 tools/testing/selftests/net/bpf/Makefile
delete mode 100644 tools/testing/selftests/net/bpf/nat6to4.c
--
1.8.3.1
next reply other threads:[~2022-10-11 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 9:57 Wang Yufen [this message]
2022-10-11 9:57 ` [net 1/2] selftests/net: fix opening object file failed Wang Yufen
2022-10-13 1:51 ` Martin KaFai Lau
2022-10-18 2:57 ` wangyufen
2022-10-18 9:50 ` wangyufen
2022-10-18 16:26 ` Alexei Starovoitov
2022-10-18 18:00 ` Jakub Kicinski
2022-10-19 1:30 ` Martin KaFai Lau
2022-10-19 1:53 ` Jakub Kicinski
2022-10-11 9:57 ` [net 2/2] selftests/net: fix missing xdp_dummy Wang Yufen
2022-10-11 16:27 ` Daniel Müller
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=1665482267-30706-1-git-send-email-wangyufen@huawei.com \
--to=wangyufen@huawei.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=deso@posteo.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lina.wang@mediatek.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).