[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNMXOn_N=9CY2iGLC=r=FAP4J2EFJbwDsAEuhKydwh6wtg@mail.gmail.com>
Date: Mon, 1 Jul 2024 10:07:29 +0200
From: Marco Elver <elver@...gle.com>
To: Thorsten Blum <thorsten.blum@...lux.com>, "Paul E. McKenney" <paulmck@...nel.org>
Cc: dvyukov@...gle.com, kasan-dev@...glegroups.com,
linux-kernel@...r.kernel.org, David.Laight@...lab.com
Subject: Re: [PATCH v3] kcsan: Use min() to fix Coccinelle warning
On Sun, 30 Jun 2024 at 22:03, Thorsten Blum <thorsten.blum@...lux.com> wrote:
>
> Fixes the following Coccinelle/coccicheck warning reported by
> minmax.cocci:
>
> WARNING opportunity for min()
>
> Use size_t instead of int for the result of min().
>
> Compile-tested with CONFIG_KCSAN=y.
>
> Reviewed-by: Marco Elver <elver@...gle.com>
> Signed-off-by: Thorsten Blum <thorsten.blum@...lux.com>
> ---
> Changes in v2:
> - Add const and remove redundant parentheses as suggested by Marco Elver
> - Link to v1: https://lore.kernel.org/linux-kernel/20240623220606.134718-2-thorsten.blum@toblux.com/
>
> Changes in v3:
> - Remove const again after feedback from David Laight
I think I was clear that the removal of const was not needed in this
case, and my preference was to keep const.
While general and _constructive_ comments are helpful and appreciated,
this level of nit-picking and bikeshedding about 'const' is a complete
and utter waste of time. I'm sorry, but I'm rather allergic to this
level of time-wasting.
As KCSAN maintainer, I'm just going to say I prefer v2.
> - Link to v2: https://lore.kernel.org/linux-kernel/20240624175727.88012-2-thorsten.blum@toblux.com/
[+Cc Paul]
Paul, if possible kindly pick v2 of this patch into the KCSAN tree:
https://lore.kernel.org/linux-kernel/20240624175727.88012-2-thorsten.blum@toblux.com/
Many thanks,
-- Marco
Powered by blists - more mailing lists