]> www.infradead.org Git - nvme.git/commit
minmax: don't use max() in situations that want a C constant expression
authorLinus Torvalds <torvalds@linux-foundation.org>
Mon, 29 Jul 2024 00:32:05 +0000 (17:32 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Mon, 29 Jul 2024 03:23:27 +0000 (20:23 -0700)
commitcb04e8b1d2f24c4c2c92f7b7529031fc35a16fed
tree78d27543d36ecb38102070bf5e640551f4ebfdae
parent9f499b8c791d2983c0a31a543c51d1b2f15e8755
minmax: don't use max() in situations that want a C constant expression

We only had a couple of array[] declarations, and changing them to just
use 'MAX()' instead of 'max()' fixes the issue.

This will allow us to simplify our min/max macros enormously, since they
can now unconditionally use temporary variables to avoid using the
argument values multiple times.

Cc: David Laight <David.Laight@aculab.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
drivers/gpu/drm/amd/pm/swsmu/smu_cmn.c
drivers/input/touchscreen/cyttsp4_core.c
drivers/irqchip/irq-sun6i-r.c
drivers/net/can/usb/etas_es58x/es58x_devlink.c
fs/btrfs/tree-checker.c
lib/vsprintf.c