[PATCH 0/7 6.12.y] Backport minmax.h updates from v6.17-rc7

Eliav Farber posted 7 patches 1 week, 2 days ago
There is a newer version of this series
include/linux/minmax.h | 205 +++++++++++++++++++----------------------
1 file changed, 95 insertions(+), 110 deletions(-)
[PATCH 0/7 6.12.y] Backport minmax.h updates from v6.17-rc7
Posted by Eliav Farber 1 week, 2 days ago
This series backports 7 patches to update minmax.h in the 6.12.y branch,
aligning it with v6.17-rc7.

The ultimate goal is to synchronize all longterm branches so that they
include the full set of minmax.h changes.

The key motivation is to bring in commit d03eba99f5bf ("minmax: allow
min()/max()/clamp() if the arguments have the same signedness"), which
is missing in older kernels.

In mainline, this change enables min()/max()/clamp() to accept mixed
argument types, provided both have the same signedness. Without it,
backported patches that use these forms may trigger compiler warnings,
which escalate to build failures when -Werror is enabled.

David Laight (7):
  minmax.h: add whitespace around operators and after commas
  minmax.h: update some comments
  minmax.h: reduce the #define expansion of min(), max() and clamp()
  minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp()
  minmax.h: move all the clamp() definitions after the min/max() ones
  minmax.h: simplify the variants of clamp()
  minmax.h: remove some #defines that are only expanded once

 include/linux/minmax.h | 205 +++++++++++++++++++----------------------
 1 file changed, 95 insertions(+), 110 deletions(-)

-- 
2.47.3
Re: [PATCH 0/7 6.12.y] Backport minmax.h updates from v6.17-rc7
Posted by Greg KH 1 week, 2 days ago
On Mon, Sep 22, 2025 at 10:31:16AM +0000, Eliav Farber wrote:
> This series backports 7 patches to update minmax.h in the 6.12.y branch,
> aligning it with v6.17-rc7.
> 
> The ultimate goal is to synchronize all longterm branches so that they
> include the full set of minmax.h changes.
> 
> The key motivation is to bring in commit d03eba99f5bf ("minmax: allow
> min()/max()/clamp() if the arguments have the same signedness"), which
> is missing in older kernels.
> 
> In mainline, this change enables min()/max()/clamp() to accept mixed
> argument types, provided both have the same signedness. Without it,
> backported patches that use these forms may trigger compiler warnings,
> which escalate to build failures when -Werror is enabled.

All now queued up, thanks!

greg k-h