From: Greg KH <gregkh@linuxfoundation.org>
To: Eliav Farber <farbere@amazon.com>
Cc: sashal@kernel.org, mario.limonciello@amd.com, lijo.lazar@amd.com,
David.Laight@aculab.com, arnd@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 00/12 6.6.y] Backport minmax.h updates from v6.17-rc7
Date: Tue, 30 Sep 2025 16:04:52 +0200 [thread overview]
Message-ID: <2025093045-proclaim-backwash-3b41@gregkh> (raw)
In-Reply-To: <20250929171733.20671-1-farbere@amazon.com>
On Mon, Sep 29, 2025 at 05:17:21PM +0000, Eliav Farber wrote:
> This series backports 15 patches to update minmax.h in the 6.6.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
prev parent reply other threads:[~2025-09-30 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 17:17 [PATCH v2 00/12 6.6.y] Backport minmax.h updates from v6.17-rc7 Eliav Farber
2025-09-29 17:17 ` [PATCH v2 01/12 6.6.y] minmax: make generic MIN() and MAX() macros available everywhere Eliav Farber
2025-09-29 17:17 ` [PATCH v2 02/12 6.6.y] minmax: simplify min()/max()/clamp() implementation Eliav Farber
2025-09-29 17:17 ` [PATCH v2 03/12 6.6.y] minmax: don't use max() in situations that want a C constant expression Eliav Farber
2025-09-29 17:17 ` [PATCH v2 04/12 6.6.y] minmax: improve macro expansion and type checking Eliav Farber
2025-09-29 17:17 ` [PATCH v2 05/12 6.6.y] minmax: fix up min3() and max3() too Eliav Farber
2025-09-29 17:17 ` [PATCH v2 06/12 6.6.y] minmax.h: add whitespace around operators and after commas Eliav Farber
2025-09-29 17:17 ` [PATCH v2 07/12 6.6.y] minmax.h: update some comments Eliav Farber
2025-09-29 17:17 ` [PATCH v2 08/12 6.6.y] minmax.h: reduce the #define expansion of min(), max() and clamp() Eliav Farber
2025-09-29 17:17 ` [PATCH v2 09/12 6.6.y] minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp() Eliav Farber
2025-09-29 17:17 ` [PATCH v2 10/12 6.6.y] minmax.h: move all the clamp() definitions after the min/max() ones Eliav Farber
2025-09-29 17:17 ` [PATCH v2 11/12 6.6.y] minmax.h: simplify the variants of clamp() Eliav Farber
2025-09-29 17:17 ` [PATCH v2 12/12 6.6.y] minmax.h: remove some #defines that are only expanded once Eliav Farber
2025-09-30 14:04 ` Greg KH [this message]
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=2025093045-proclaim-backwash-3b41@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=arnd@kernel.org \
--cc=farbere@amazon.com \
--cc=lijo.lazar@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=sashal@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