-
Masahiro Yamada authored
U-Boot has never cared about the type when we get max/min of two values, but Linux Kernel does. This commit gets min, max, min3, max3 macros synced with the kernel introducing type checks. Many of references of those macros must be fixed to suppress warnings. We have two options: - Use min, max, min3, max3 only when the arguments have the same type (or add casts to the arguments) - Use min_t/max_t instead with the appropriate type for the first argument Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by:
Pavel Machek <pavel@denx.de> Acked-by:
Lukasz Majewski <l.majewski@samsung.com> Tested-by:
Tom Rini <trini@ti.com>
Masahiro Yamada authoredU-Boot has never cared about the type when we get max/min of two values, but Linux Kernel does. This commit gets min, max, min3, max3 macros synced with the kernel introducing type checks. Many of references of those macros must be fixed to suppress warnings. We have two options: - Use min, max, min3, max3 only when the arguments have the same type (or add casts to the arguments) - Use min_t/max_t instead with the appropriate type for the first argument Signed-off-by:
dev.c 3.91 KiB