From: Thierry Reding <thierry.reding@gmail.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
nicolas.palix@imag.fr, michal.lkml@markovi.net,
cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] coccinnelle: Remove ptr_ret script
Date: Tue, 7 Jan 2020 10:40:33 +0100 [thread overview]
Message-ID: <20200107094033.GA1964183@ulmo> (raw)
In-Reply-To: <20200107073629.325249-1-maxime@cerno.tech>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
On Tue, Jan 07, 2020 at 08:36:29AM +0100, Maxime Ripard wrote:
> The ptr_ret script script addresses a number of situations where we end up
> testing an error pointer, and if it's an error returning it, or return 0
> otherwise to transform it into a PTR_ERR_OR_ZERO call.
>
> So it will convert a block like this:
>
> if (IS_ERR(err))
> return PTR_ERR(err);
>
> return 0;
>
> into
>
> return PTR_ERR_OR_ZERO(err);
>
> While this is technically correct, it has a number of drawbacks. First, it
> merges the error and success path, which will make it harder for a reviewer
> or reader to grasp.
>
> It's also more difficult to extend if we were to add some code between the
> error check and the function return, making the author essentially revert
> that patch before adding new lines, while it would have been a trivial
> addition otherwise for the rewiever.
>
> Therefore, since that script is only about cosmetic in the first place,
> let's remove it since it's not worth it.
>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Cc: Mark Brown <broonie@kernel.org>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
> scripts/coccinelle/api/ptr_ret.cocci | 97 ----------------------------
> 1 file changed, 97 deletions(-)
> delete mode 100644 scripts/coccinelle/api/ptr_ret.cocci
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-07 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 7:36 [PATCH] coccinnelle: Remove ptr_ret script Maxime Ripard
2020-01-07 9:40 ` Jani Nikula
2020-01-07 9:40 ` Thierry Reding [this message]
2020-01-07 10:06 ` Julia Lawall
2020-01-07 10:29 ` [Cocci] " Wolfram Sang
2020-12-15 8:48 ` Maxime Ripard
2020-12-15 8:52 ` Julia Lawall
2020-12-15 12:25 ` Maxime Ripard
2020-01-07 11:48 ` Mark Brown
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=20200107094033.GA1964183@ulmo \
--to=thierry.reding@gmail.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=broonie@kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=tomi.valkeinen@ti.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