From: Julia Lawall <julia.lawall@inria.fr>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: johan@kernel.org, Jaehee Park <jhpark1013@gmail.com>,
elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH v2 2/2] staging: greybus: remove unneeded return
Date: Wed, 13 Apr 2022 08:16:20 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2204130815020.3470@hadrien> (raw)
In-Reply-To: <5792471.alqRGMn8q6@leap>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
On Tue, 12 Apr 2022, Fabio M. De Francesco wrote:
> On martedì 12 aprile 2022 21:59:15 CEST Jaehee Park wrote:
> > An empty function with void return type does not need an explicit
> > return. Issue found by checkpatch.
> >
> > Signed-off-by: Jaehee Park <jhpark1013@gmail.com>
> > ---
> > drivers/staging/greybus/audio_codec.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/staging/greybus/audio_codec.c b/drivers/staging/
> greybus/audio_codec.c
> > index 0f50d1e51e2c..3e3a16568def 100644
> > --- a/drivers/staging/greybus/audio_codec.c
> > +++ b/drivers/staging/greybus/audio_codec.c
> > @@ -1032,7 +1032,6 @@ static int gbcodec_probe(struct snd_soc_component
> *comp)
> > static void gbcodec_remove(struct snd_soc_component *comp)
> > {
> > /* Empty function for now */
> > - return;
> > }
> >
> > static int gbcodec_write(struct snd_soc_component *comp, unsigned int
> reg,
> > --
> > 2.25.1
> >
> Hi Jaehee,
>
> If I recall it correctly, Dan Carpenter suggested to remove this empty
> function.
>
> When developers remove lines of code from a function which becomes empty
> after the removals, they also remove the resulting empty function and
> delete all the calls (if there are any left) at the same time.
It's probably not relevant in this case, but the function could be needed
if it is a branch of an ifdef. Also if it is stored in a structure field
and the user of the structure does not check for NULL.
julia
next prev parent reply other threads:[~2022-04-13 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 19:59 [PATCH v2 0/2] staging: greybus: fix warnings reported by checkpatch Jaehee Park
2022-04-12 19:59 ` [PATCH v2 1/2] staging: greybus: correct typo in comment Jaehee Park
2022-04-12 20:38 ` Alex Elder
2022-04-12 19:59 ` [PATCH v2 2/2] staging: greybus: remove unneeded return Jaehee Park
2022-04-12 20:35 ` Alex Elder
2022-04-13 4:43 ` Jaehee Park
2022-04-12 20:35 ` Fabio M. De Francesco
2022-04-13 4:44 ` Jaehee Park
2022-04-13 6:16 ` Julia Lawall [this message]
2022-04-13 6:35 ` Fabio M. De Francesco
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=alpine.DEB.2.22.394.2204130815020.3470@hadrien \
--to=julia.lawall@inria.fr \
--cc=elder@kernel.org \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jhpark1013@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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