[PATCH v3 29/32] selftests/nolibc: rename vfprintf test suite

[Thomas Weißschuh]

With the addition of snprintf() and its usage in nolibc-test, the name of
the "vfprintf" test suite is not accurate anymore.

Rename the suite to be more generic.

Signed-off-by: Thomas Weißschuh <thomas.weisssc...@linutronix.de>
Acked-by: Willy Tarreau <w...@1wt.eu>
---
 tools/testing/selftests/nolibc/nolibc-test.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/nolibc/nolibc-test.c 
b/tools/testing/selftests/nolibc/nolibc-test.c
index 
8fb241af33cbba2ceb1303bf41582d51f70df68e..6dfa94df37547dae46ab19195a763fe22b065bab
 100644
--- a/tools/testing/selftests/nolibc/nolibc-test.c
+++ b/tools/testing/selftests/nolibc/nolibc-test.c
@@ -1390,7 +1390,7 @@ static int test_scanf(void)
        return 0;
 }
 
-static int run_vfprintf(int min, int max)
+static int run_printf(int min, int max)
 {
        int test;
        int ret = 0;
@@ -1551,7 +1551,7 @@ static const struct test test_names[] = {
        { .name = "startup",    .func = run_startup    },
        { .name = "syscall",    .func = run_syscall    },
        { .name = "stdlib",     .func = run_stdlib     },
-       { .name = "vfprintf",   .func = run_vfprintf   },
+       { .name = "printf",     .func = run_printf     },
        { .name = "protection", .func = run_protection },
        { 0 }
 };

-- 
2.49.0