selftests/nolibc: use INT_MAX instead of __INT_MAX__

nolibc now has INT_MAX in stdint.h, so, don't mix INT_MAX and
__INT_MAX__, unify them to INT_MAX.

Signed-off-by: Zhangjin Wu <falcon@tinylab.org>
Reviewed-by: Thomas Weißschuh <linux@weissschuh.net>
Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>

diff --git a/tools/testing/selftests/nolibc/nolibc-test.c b/tools/testing/selftests/nolibc/nolibc-test.c
index 7d4b8d12050d03b77ce84884476cc3239bb0f8c6..ff3da953980959b91b0a4c74b64b181cbfb17725 100644 (file)
--- a/tools/testing/selftests/nolibc/nolibc-test.c
+++ b/tools/testing/selftests/nolibc/nolibc-test.c
@@ -936,7 +936,7 @@ static const struct test test_names[] = {
 int main(int argc, char **argv, char **envp)
 {
        int min = 0;
-       int max = __INT_MAX__;
+       int max = INT_MAX;
        int ret = 0;
        int err;
        int idx;
@@ -984,7 +984,7 @@ int main(int argc, char **argv, char **envp)
                                 * here, which defaults to the full range.
                                 */
                                do {
-                                       min = 0; max = __INT_MAX__;
+                                       min = 0; max = INT_MAX;
                                        value = colon;
                                        if (value && *value) {
                                                colon = strchr(value, ':');