From: linux@treblig.org
To: andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
kpsingh@kernel.org, shuah@kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH 1/3] selftests/bpf: remove unused struct 'scale_test_def'
Date: Mon, 3 Jun 2024 00:41:10 +0100 [thread overview]
Message-ID: <20240602234112.225107-2-linux@treblig.org> (raw)
In-Reply-To: <20240602234112.225107-1-linux@treblig.org>
From: "Dr. David Alan Gilbert" <linux@treblig.org>
'scale_test_def' is unused since
commit 3762a39ce85f ("selftests/bpf: Split out bpf_verif_scale selftests
into multiple tests").
Remove it.
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
---
tools/testing/selftests/bpf/prog_tests/bpf_verif_scale.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/tools/testing/selftests/bpf/prog_tests/bpf_verif_scale.c b/tools/testing/selftests/bpf/prog_tests/bpf_verif_scale.c
index 4c6ada5b270b..73f669014b69 100644
--- a/tools/testing/selftests/bpf/prog_tests/bpf_verif_scale.c
+++ b/tools/testing/selftests/bpf/prog_tests/bpf_verif_scale.c
@@ -45,12 +45,6 @@ static int check_load(const char *file, enum bpf_prog_type type)
return err;
}
-struct scale_test_def {
- const char *file;
- enum bpf_prog_type attach_type;
- bool fails;
-};
-
static void scale_test(const char *file,
enum bpf_prog_type attach_type,
bool should_fail)
--
2.45.1
next prev parent reply other threads:[~2024-06-02 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 23:41 [PATCH 0/3] Dead structs in tools/testing/selftests/bpf linux
2024-06-02 23:41 ` linux [this message]
2024-06-02 23:41 ` [PATCH 2/3] selftests/bpf: remove unused 'key_t' structs linux
2024-06-02 23:41 ` [PATCH 3/3] selftests/bpf: remove unused struct 'libcap' linux
2024-06-03 15:00 ` [PATCH 0/3] Dead structs in tools/testing/selftests/bpf 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=20240602234112.225107-2-linux@treblig.org \
--to=linux@treblig.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mykolal@fb.com \
--cc=shuah@kernel.org \
/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