mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gal Pressman <gal@nvidia.com>
To: Johan Hovold <johan@kernel.org>
Cc: Julia Lawall <Julia.Lawall@inria.fr>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Jakub Kicinski <kuba@kernel.org>,
	Alexei Lazar <alazar@nvidia.com>, Simon Horman <horms@kernel.org>,
	cocci@inria.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "scripts/coccinelle: Find PTR_ERR() to %pe candidates"
Date: Thu, 30 Oct 2025 16:36:46 +0200	[thread overview]
Message-ID: <9c32fa45-2b8f-4005-94cd-a9755981cff5@nvidia.com> (raw)
In-Reply-To: <aQNw5NqZSZk5JNxn@hovoldconsulting.com>

On 30/10/2025 16:06, Johan Hovold wrote:
> Note that in most cases you have ret variable that holds the errno,
> which would not be caught by this cocci script either:
> 
> 	ret = PTR_ERR(p);
> 	dev_err(dev, "failed to ...: %d\n", ret);
> 	return ret; // or goto out;

I have a followup patch that catches these kinds of cases as well.

> It still generates noise and extra work for already overworked
> maintainers that would need to explain over and over again why they are
> rejecting patches that appears to fix "warnings". Some will just take
> the patches, which leads to inconsistencies (as only a handful of
> printks will be converted) and a push for a style which again only some
> people prefer.

There's the subsystem maintainer "rules" documentation in
Documentation/process/maintainer-*.rst which can document these kinds of
stuff.

> 
> So I still think this script should be dropped. And you still need to
> review drivers manually if you really want to use %pe consistently (e.g.
> for all the cases where there is no error pointer to begin with).

I am not sure who is to decide, obviously I prefer not to revert it, but
I understand your concerns.

  reply	other threads:[~2025-10-30 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 13:29 Johan Hovold
2025-10-29 13:59 ` Gal Pressman
2025-10-29 14:04   ` Julia Lawall
2025-10-29 17:26     ` Jakub Kicinski
2025-10-29 16:38   ` Johan Hovold
2025-10-29 17:00     ` [cocci] " Markus Elfring
2025-10-29 17:35     ` [PATCH] " Gal Pressman
2025-10-30 14:06       ` Johan Hovold
2025-10-30 14:36         ` Gal Pressman [this message]
2025-10-31 14:10           ` Johan Hovold
2025-10-30  7:36     ` Julia Lawall

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=9c32fa45-2b8f-4005-94cd-a9755981cff5@nvidia.com \
    --to=gal@nvidia.com \
    --cc=Julia.Lawall@inria.fr \
    --cc=alazar@nvidia.com \
    --cc=cocci@inria.fr \
    --cc=horms@kernel.org \
    --cc=johan@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.palix@imag.fr \
    /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

all inboxes | Powered by JetHome®