[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7430fd6f-ead2-4ff8-8329-0c0875a39611@kernel.org>
Date: Thu, 20 Nov 2025 10:20:41 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: david.laight.linux@...il.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Axel Rasmussen <axelrasmussen@...gle.com>, Christoph Lameter
<cl@...two.org>, Dennis Zhou <dennis@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Mike Rapoport <rppt@...nel.org>, Tejun Heo <tj@...nel.org>,
Yuanchu Xie <yuanchu@...gle.com>
Subject: Re: [PATCH 39/44] mm: use min() instead of min_t()
On 11/19/25 23:41, david.laight.linux@...il.com wrote:
> From: David Laight <david.laight.linux@...il.com>
>
> min_t(unsigned int, a, b) casts an 'unsigned long' to 'unsigned int'.
> Use min(a, b) instead as it promotes any 'unsigned int' to 'unsigned long'
> and so cannot discard significant bits.
I thought using min() was frowned upon and we were supposed to use
min_t() instead to make it clear which type we want to use.
Do I misremember or have things changed?
Wasn't there a checkpatch warning that states exactly that?
--
Cheers
David
Powered by blists - more mailing lists