From: Markus Elfring <Markus.Elfring@web.de>
To: Johan Hovold <johan@kernel.org>, Gal Pressman <gal@nvidia.com>,
cocci@inria.fr, Jakub Kicinski <kuba@kernel.org>,
Julia Lawall <Julia.Lawall@inria.fr>
Cc: LKML <linux-kernel@vger.kernel.org>,
Alexei Lazar <alazar@nvidia.com>,
Nicolas Palix <nicolas.palix@imag.fr>,
Simon Horman <horms@kernel.org>
Subject: Re: [cocci] Revert "scripts/coccinelle: Find PTR_ERR() to %pe candidates"
Date: Wed, 29 Oct 2025 18:00:12 +0100 [thread overview]
Message-ID: <aee265c7-eced-45e8-b016-0dffa5d415a9@web.de> (raw)
In-Reply-To: <aQJDIz-8Ow0OmczH@hovoldconsulting.com>
>> The test by no means mandates authors to use %pe, as the output says:
>> WARNING: Consider using %pe to print PTR_ERR()
>>
>> "Consider" :).
>
> Right, but it's preceded by a big "WARNING".
Would you find an other message prefix nicer?
>> I would consider it best practice to use it, and a few drivers were
>> converted thanks to this test.
Would there be more convincing arguments needed according to better practice?
> Unlike the rest of the misc cocci scripts I skimmed, this one does not
> guard against any bugs. Instead it's pushing for a subjective style
> preference, which is just going to result in churn when the clean up
> crew starts sending mindless conversions of individual printks.
>
> By all means, use %pe for your drivers, but it should not be forced
> upon the rest of us this way.
Is there a need to mark any more SmPL scripts as “controversial”?
>> If the issue is with automatic build bots, then maybe this test should
>> be excluded from them, rather than deleted?
>
> It's both; it's the noise the new warnings generate but also the coming
> flood up patches to "fix" them. There are already some 40 commits or so
> in linux-next referencing this script.
How will the change tolerance evolve further?
Regards,
Markus
next prev parent reply other threads:[~2025-10-29 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 13:29 [cocci] [PATCH] Revert "scripts/coccinelle: Find PTR_ERR() to %pe candidates" 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 ` Markus Elfring [this message]
2025-10-29 17:35 ` Gal Pressman
2025-10-30 14:06 ` Johan Hovold
2025-10-30 14:36 ` Gal Pressman
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=aee265c7-eced-45e8-b016-0dffa5d415a9@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=alazar@nvidia.com \
--cc=cocci@inria.fr \
--cc=gal@nvidia.com \
--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