staging: lustre: use min/max instead of MIN/MAX, simple cases
authorJeremiah Mahler <jmmahler@gmail.com>
Fri, 26 Dec 2014 00:04:41 +0000 (16:04 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 17 Jan 2015 23:49:21 +0000 (15:49 -0800)
commit0c5754178d8b39e5709da82873f0a6d975ea92f5
treeecbf6448111a40f2a03567938ad59439094ba82a
parent3f3af378f5d7e9085496a064ef2b0c3b35a8a62c
staging: lustre: use min/max instead of MIN/MAX, simple cases

Custom MIN/MAX operations are being used which are not as robust
as the built in min/max operations which will warn about potentially
problematic type comparisons.

For the simple cases, where no type warning is produced, simply
replace MIN/MAX with min/max.

Signed-off-by: Jeremiah Mahler <jmmahler@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c
drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c
drivers/staging/lustre/lnet/klnds/socklnd/socklnd_cb.c
drivers/staging/lustre/lnet/lnet/lib-move.c
drivers/staging/lustre/lnet/lnet/router.c
drivers/staging/lustre/lnet/selftest/conrpc.h
drivers/staging/lustre/lnet/selftest/rpc.c
drivers/staging/lustre/lustre/libcfs/linux/linux-tracefile.c