Commit a36cfc5e authored by @wuzhangjin's avatar @wuzhangjin Committed by Paul E. McKenney
Browse files

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: default avatarZhangjin Wu <falcon@tinylab.org>
Reviewed-by: default avatarThomas Weißschuh <linux@weissschuh.net>
Signed-off-by: default avatarWilly Tarreau <w@1wt.eu>
Signed-off-by: default avatarPaul E. McKenney <paulmck@kernel.org>
parent bd27fef3

tools/testing/selftests/nolibc/nolibc-test.c

+2 −2
Original line number Diff line number Diff line
@@ -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, ':');