public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Thorsten Blum <thorsten.blum@toblux.com>,
	jstultz@google.com, sboyd@kernel.org,
	linux-kernel@vger.kernel.org
Cc: Thorsten Blum <thorsten.blum@toblux.com>
Subject: Re: [PATCH] timekeeping: Use min() to fix Coccinelle warning
Date: Tue, 25 Jun 2024 08:36:11 +0200	[thread overview]
Message-ID: <87jzid7cmc.ffs@tglx> (raw)
In-Reply-To: <20240624062411.321995-2-thorsten.blum@toblux.com>

Thorsten!

On Mon, Jun 24 2024 at 08:24, Thorsten Blum wrote:

> Fixes the following Coccinelle/coccicheck warning reported by
> minmax.cocci:
>
> 	WARNING opportunity for min()

I'm fine with the change, but not so much with the change log.

You cannot fix a coccinelle warning. You can only fix the code which
triggers the warning, right?

'Opportunity to use min()' is nothing else than an opportunity, but
what's the benefit of replacing correct code with it? What does this
fix?

It fixes nothing. So calling it a fix is confusing at best.

What you want to say is something like this:

  Subject: timekeeping: Replace open coded min()

  Replace open coded min() because $GOOD_REASON

  Discovered by minmax.cocci

$GOOD_REASON is not 'coccinelle emitted a warning'.

Thanks,

        tglx

  parent reply	other threads:[~2024-06-25  6:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24  6:24 [PATCH] timekeeping: Use min() to fix Coccinelle warning Thorsten Blum
2024-06-24 18:30 ` John Stultz
2024-06-25  6:36 ` Thomas Gleixner [this message]
2024-06-29 23:12   ` Thorsten Blum
2024-07-10 21:23     ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2024-06-26  5:36 Thorsten Blum

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=87jzid7cmc.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=thorsten.blum@toblux.com \
    /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