From: Greg KH <gregkh@linuxfoundation.org>
To: David.Laight@aculab.com, Rodrigo.Siqueira@amd.com,
Xinhui.Pan@amd.com, agk@redhat.com, airlied@gmail.com,
akpm@linux-foundation.org, alexander.deucher@amd.com,
alexandre.torgue@foss.st.com, amd-gfx@lists.freedesktop.org,
andriy.shevchenko@linux.intel.com,
anton.ivanov@cambridgegreys.com, arnd@kernel.org,
artur.paszkiewicz@intel.com, bp@alien8.de,
christian.koenig@amd.com, clm@fb.com, daniel@ffwll.ch,
dave.hansen@linux.intel.com, davem@davemloft.net,
dm-devel@lists.linux.dev, dmitry.torokhov@gmail.com,
dri-devel@lists.freedesktop.org, dsahern@kernel.org,
dsterba@suse.com, edumazet@google.com, evan.quan@amd.com,
farbere@amazon.com, harry.wentland@amd.com, hdegoede@redhat.com,
hpa@zytor.com, ilpo.jarvinen@linux.intel.com,
james.morse@arm.com, jdelvare@suse.com, jejb@linux.ibm.com,
jernej.skrabec@gmail.com, joabreu@synopsys.com,
johannes@sipsolutions.net, josef@toxicpanda.com,
keescook@chromium.org, krzysztof.kozlowski@linaro.org,
kuba@kernel.org, linus.walleij@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
linux-staging@lists.linux.dev,
linux-stm32@st-md-mailman.stormreply.com,
linux-sunxi@lists.linux.dev, linux-um@lists.infradead.org,
linux@rasmusvillemoes.dk, linux@roeck-us.net,
lorenzo.stoakes@oracle.com, luc.vanoostenryck@gmail.com,
luto@kernel.org, maarten.lankhorst@linux.intel.com,
mailhol.vincent@wanadoo.fr, malattia@linux.it,
markgross@kernel.org, martin.petersen@oracle.com,
mchehab@kernel.org, mcoquelin.stm32@gmail.com,
mhiramat@kernel.org, minchan@kernel.org, mingo@redhat.com,
mkl@pengutronix.de, mripard@kernel.org, pabeni@redhat.com,
peterz@infradead.org, pmladek@suse.com, qiuxu.zhuo@intel.com,
richard@nod.at, rostedt@goodmis.org, rric@kernel.org,
sakari.ailus@linux.intel.com, samuel@sholland.org,
senozhatsky@chromium.org, shuah@kernel.org, snitzer@kernel.org,
sunpeng.li@amd.com, tglx@linutronix.de, tony.luck@intel.com,
torvalds@linux-foundation.org, tzimmermann@suse.de,
wad@chromium.org, wens@csie.org, wg@grandegger.com,
x86@kernel.org
Cc: stable-commits@vger.kernel.org
Subject: Re: Patch "minmax: make generic MIN() and MAX() macros available everywhere" has been added to the 6.6-stable tree
Date: Mon, 22 Sep 2025 14:40:48 +0200 [thread overview]
Message-ID: <2025092209-owl-whisking-03e3@gregkh> (raw)
In-Reply-To: <2025092200-reverb-stumble-8578@gregkh>
On Mon, Sep 22, 2025 at 02:27:00PM +0200, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> minmax: make generic MIN() and MAX() macros available everywhere
>
> to the 6.6-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> minmax-make-generic-min-and-max-macros-available-everywhere.patch
> and it can be found in the queue-6.6 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
> >From prvs=353d6d59a=farbere@amazon.com Mon Sep 22 12:35:15 2025
> From: Eliav Farber <farbere@amazon.com>
> Date: Mon, 22 Sep 2025 10:32:30 +0000
> Subject: minmax: make generic MIN() and MAX() macros available everywhere
> To: <richard@nod.at>, <anton.ivanov@cambridgegreys.com>, <johannes@sipsolutions.net>, <dave.hansen@linux.intel.com>, <luto@kernel.org>, <peterz@infradead.org>, <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>, <x86@kernel.org>, <hpa@zytor.com>, <tony.luck@intel.com>, <qiuxu.zhuo@intel.com>, <james.morse@arm.com>, <mchehab@kernel.org>, <rric@kernel.org>, <harry.wentland@amd.com>, <sunpeng.li@amd.com>, <Rodrigo.Siqueira@amd.com>, <alexander.deucher@amd.com>, <christian.koenig@amd.com>, <Xinhui.Pan@amd.com>, <airlied@gmail.com>, <daniel@ffwll.ch>, <evan.quan@amd.com>, <maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>, <tzimmermann@suse.de>, <jdelvare@suse.com>, <linux@roeck-us.net>, <linus.walleij@linaro.org>, <dmitry.torokhov@gmail.com>, <wens@csie.org>, <jernej.skrabec@gmail.com>, <samuel@sholland.org>, <agk@redhat.com>, <snitzer@kernel.org>, <dm-devel@lists.linux.dev>, <mailhol.vincent@wanadoo.fr>, <wg@grandegger.com>, <mkl@pengutronix.de>, <davem@davemloft.net>, <edu
> mazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>, <alexandre.torgue@foss.st.com>, <joabreu@synopsys.com>, <mcoquelin.stm32@gmail.com>, <krzysztof.kozlowski@linaro.org>, <malattia@linux.it>, <hdegoede@redhat.com>, <ilpo.jarvinen@linux.intel.com>, <markgross@kernel.org>, <artur.paszkiewicz@intel.com>, <jejb@linux.ibm.com>, <martin.petersen@oracle.com>, <sakari.ailus@linux.intel.com>, <gregkh@linuxfoundation.org>, <clm@fb.com>, <josef@toxicpanda.com>, <dsterba@suse.com>, <luc.vanoostenryck@gmail.com>, <rostedt@goodmis.org>, <mhiramat@kernel.org>, <pmladek@suse.com>, <andriy.shevchenko@linux.intel.com>, <linux@rasmusvillemoes.dk>, <senozhatsky@chromium.org>, <minchan@kernel.org>, <akpm@linux-foundation.org>, <dsahern@kernel.org>, <shuah@kernel.org>, <keescook@chromium.org>, <wad@chromium.org>, <farbere@amazon.com>, <David.Laight@ACULAB.COM>, <arnd@kernel.org>, <linux-um@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <linux-edac@vger.kernel.org>, <amd-gfx@lists.freedeskto
> p.org>, <dri-devel@lists.freedesktop.org>, <linux-hwmon@vger.kernel.org>, <linux-input@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-sunxi@lists.linux.dev>, <linux-media@vger.kernel.org>, <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <platform-driver-x86@vger.kernel.org>, <linux-scsi@vger.kernel.org>, <linux-staging@lists.linux.dev>, <linux-btrfs@vger.kernel.org>, <linux-sparse@vger.kernel.org>, <linux-trace-kernel@vger.kernel.org>, <linux-mm@kvack.org>, <linux-kselftest@vger.kernel.org>, <bpf@vger.kernel.org>, <stable@vger.kernel.org>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>, David Laight <David.Laight@aculab.com>, Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> Message-ID: <20250922103241.16213-5-farbere@amazon.com>
>
> From: Linus Torvalds <torvalds@linux-foundation.org>
>
> [ Upstream commit 1a251f52cfdc417c84411a056bc142cbd77baef4 ]
>
> This just standardizes the use of MIN() and MAX() macros, with the very
> traditional semantics. The goal is to use these for C constant
> expressions and for top-level / static initializers, and so be able to
> simplify the min()/max() macros.
>
> These macro names were used by various kernel code - they are very
> traditional, after all - and all such users have been fixed up, with a
> few different approaches:
>
> - trivial duplicated macro definitions have been removed
>
> Note that 'trivial' here means that it's obviously kernel code that
> already included all the major kernel headers, and thus gets the new
> generic MIN/MAX macros automatically.
>
> - non-trivial duplicated macro definitions are guarded with #ifndef
>
> This is the "yes, they define their own versions, but no, the include
> situation is not entirely obvious, and maybe they don't get the
> generic version automatically" case.
>
> - strange use case #1
>
> A couple of drivers decided that the way they want to describe their
> versioning is with
>
> #define MAJ 1
> #define MIN 2
> #define DRV_VERSION __stringify(MAJ) "." __stringify(MIN)
>
> which adds zero value and I just did my Alexander the Great
> impersonation, and rewrote that pointless Gordian knot as
>
> #define DRV_VERSION "1.2"
>
> instead.
>
> - strange use case #2
>
> A couple of drivers thought that it's a good idea to have a random
> 'MIN' or 'MAX' define for a value or index into a table, rather than
> the traditional macro that takes arguments.
>
> These values were re-written as C enum's instead. The new
> function-line macros only expand when followed by an open
> parenthesis, and thus don't clash with enum use.
>
> Happily, there weren't really all that many of these cases, and a lot of
> users already had the pattern of using '#ifndef' guarding (or in one
> case just using '#undef MIN') before defining their own private version
> that does the same thing. I left such cases alone.
>
> Cc: David Laight <David.Laight@aculab.com>
> Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Eliav Farber <farbere@amazon.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> arch/um/drivers/mconsole_user.c | 2
> drivers/edac/skx_common.h | 1
> drivers/gpu/drm/amd/display/modules/hdcp/hdcp_ddc.c | 2
> drivers/gpu/drm/amd/pm/powerplay/hwmgr/ppevvmath.h | 14 ++++-
Oops, nope, this patch breaks the amd driver's build :(
I'll drop this patch and stop here on this patch series. Please fix
this up and resend the remaining ones after it builds properly.
thanks,
greg k-h
next prev parent reply other threads:[~2025-09-22 12:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 10:32 [PATCH 00/15 v6.6.y] Backport minmax.h updates from v6.17-rc7 Eliav Farber
2025-09-22 10:32 ` [PATCH 01/15 6.6.y] minmax: avoid overly complicated constant expressions in VM code Eliav Farber
2025-09-22 12:26 ` Patch "minmax: avoid overly complicated constant expressions in VM code" has been added to the 6.6-stable tree gregkh
2025-09-22 10:32 ` [PATCH 02/15 6.6.y] minmax: simplify and clarify min_t()/max_t() implementation Eliav Farber
2025-09-22 12:27 ` Patch "minmax: simplify and clarify min_t()/max_t() implementation" has been added to the 6.6-stable tree gregkh
2025-09-22 10:32 ` [PATCH 03/15 6.6.y] minmax: add a few more MIN_T/MAX_T users Eliav Farber
2025-09-22 12:26 ` Patch "minmax: add a few more MIN_T/MAX_T users" has been added to the 6.6-stable tree gregkh
2025-09-22 10:32 ` [PATCH 04/15 6.6.y] minmax: make generic MIN() and MAX() macros available everywhere Eliav Farber
2025-09-22 12:27 ` Patch "minmax: make generic MIN() and MAX() macros available everywhere" has been added to the 6.6-stable tree gregkh
2025-09-22 12:40 ` Greg KH [this message]
2025-09-22 10:32 ` [PATCH 05/15 6.6.y] minmax: simplify min()/max()/clamp() implementation Eliav Farber
2025-09-22 12:27 ` Patch "minmax: simplify min()/max()/clamp() implementation" has been added to the 6.6-stable tree gregkh
2025-09-22 10:32 ` [PATCH 06/15 6.6.y] minmax: don't use max() in situations that want a C constant expression Eliav Farber
2025-09-22 12:26 ` Patch "minmax: don't use max() in situations that want a C constant expression" has been added to the 6.6-stable tree gregkh
2025-09-22 10:32 ` [PATCH 07/15 6.6.y] minmax: improve macro expansion and type checking Eliav Farber
2025-09-22 12:26 ` Patch "minmax: improve macro expansion and type checking" has been added to the 6.6-stable tree gregkh
2025-09-22 10:32 ` [PATCH 08/15 6.6.y] minmax: fix up min3() and max3() too Eliav Farber
2025-09-22 12:26 ` Patch "minmax: fix up min3() and max3() too" has been added to the 6.6-stable tree gregkh
2025-09-22 10:32 ` [PATCH 09/15 6.6.y] minmax.h: add whitespace around operators and after commas Eliav Farber
2025-09-22 10:32 ` [PATCH 10/15 6.6.y] minmax.h: update some comments Eliav Farber
2025-09-22 10:32 ` [PATCH 11/15 6.6.y] minmax.h: reduce the #define expansion of min(), max() and clamp() Eliav Farber
2025-09-22 10:32 ` [PATCH 12/15 6.6.y] minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp() Eliav Farber
2025-09-22 10:32 ` [PATCH 13/15 6.6.y] minmax.h: move all the clamp() definitions after the min/max() ones Eliav Farber
2025-09-22 10:32 ` [PATCH 14/15 6.6.y] minmax.h: simplify the variants of clamp() Eliav Farber
2025-09-22 10:32 ` [PATCH 15/15 6.6.y] minmax.h: remove some #defines that are only expanded once Eliav Farber
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=2025092209-owl-whisking-03e3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=agk@redhat.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=arnd@kernel.org \
--cc=artur.paszkiewicz@intel.com \
--cc=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=clm@fb.com \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dm-devel@lists.linux.dev \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsahern@kernel.org \
--cc=dsterba@suse.com \
--cc=edumazet@google.com \
--cc=evan.quan@amd.com \
--cc=farbere@amazon.com \
--cc=harry.wentland@amd.com \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=jdelvare@suse.com \
--cc=jejb@linux.ibm.com \
--cc=jernej.skrabec@gmail.com \
--cc=joabreu@synopsys.com \
--cc=johannes@sipsolutions.net \
--cc=josef@toxicpanda.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-um@lists.infradead.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=lorenzo.stoakes@oracle.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=luto@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mailhol.vincent@wanadoo.fr \
--cc=malattia@linux.it \
--cc=markgross@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mhiramat@kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=mkl@pengutronix.de \
--cc=mripard@kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=qiuxu.zhuo@intel.com \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=rric@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=samuel@sholland.org \
--cc=senozhatsky@chromium.org \
--cc=shuah@kernel.org \
--cc=snitzer@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=sunpeng.li@amd.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
--cc=wad@chromium.org \
--cc=wens@csie.org \
--cc=wg@grandegger.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).