dlan17/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

selftests/nolibc: use INT_MAX instead of __INT_MAX__

Browse Source 
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>
This commit is contained in:
Zhangjin Wu
2023-06-09 11:46:09 -07:00
committed by Paul E. McKenney
parent bd27fef329
commit a36cfc5e48
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/testing/selftests/nolibc/nolibc-test.c
+2 -2
View File
@@ -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, ':');