selftests/nolibc: use INT_MAX instead of __INT_MAX__
authorZhangjin Wu <falcon@tinylab.org>
Sat, 3 Jun 2023 08:08:12 +0000 (16:08 +0800)
committerPaul E. McKenney <paulmck@kernel.org>
Fri, 9 Jun 2023 18:46:09 +0000 (11:46 -0700)
commita36cfc5e483e7bf609b3d39d83150626d92355e0
tree2e35c1fb0c57d879b7f6a2442c1465dc2fec0721
parentbd27fef32960f5c9da57a50d58aa9f0bf0a3ff54
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>
tools/testing/selftests/nolibc/nolibc-test.c