Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Eliav Farber <farbere@amazon.com>
To: <farbere@amazon.com>, <akpm@linux-foundation.org>,
	<David.Laight@ACULAB.COM>, <arnd@kernel.org>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: [PATCH 0/7 6.12.y] Backport minmax.h updates from v6.17-rc7
Date: Mon, 22 Sep 2025 10:31:16 +0000	[thread overview]
Message-ID: <20250922103123.14538-1-farbere@amazon.com> (raw)

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


             reply	other threads:[~2025-09-22 10:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 10:31 Eliav Farber [this message]
2025-09-22 10:31 ` [PATCH 1/7 6.12.y] minmax.h: add whitespace around operators and after commas Eliav Farber
2025-09-22 10:31 ` [PATCH 2/7 6.12.y] minmax.h: update some comments Eliav Farber
2025-09-22 10:31 ` [PATCH 3/7 6.12.y] minmax.h: reduce the #define expansion of min(), max() and clamp() Eliav Farber
2025-09-22 10:31 ` [PATCH 4/7 6.12.y] minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp() Eliav Farber
2025-09-22 10:31 ` [PATCH 5/7 6.12.y] minmax.h: move all the clamp() definitions after the min/max() ones Eliav Farber
2025-09-22 12:14   ` Greg KH
2025-09-22 10:31 ` [PATCH 6/7 6.12.y] minmax.h: simplify the variants of clamp() Eliav Farber
2025-09-22 10:31 ` [PATCH 7/7 6.12.y] minmax.h: remove some #defines that are only expanded once Eliav Farber
2025-09-22 12:16 ` [PATCH 0/7 6.12.y] Backport minmax.h updates from v6.17-rc7 Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250922103123.14538-1-farbere@amazon.com \
    --to=farbere@amazon.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox