From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Colin King <colin.king@canonical.com>,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
xen-devel@lists.xenproject.org, alsa-devel@alsa-project.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] ALSA: xen-front: remove redundant error check on ret
Date: Mon, 28 May 2018 07:42:12 +0900 [thread overview]
Message-ID: <ee539e2d-568e-4bfa-a4aa-4a9b39bc1bd8@sakamocchi.jp> (raw)
In-Reply-To: <20180527212312.23997-1-colin.king@canonical.com>
Hi,
On May 28 2018 06:23, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The error for a -ve value in ret is redundant as all previous
> assignments to ret have an associated -ve check and hence it
> is impossible for ret to be less that zero at the point of the
> check. Remove this redundant error check.
>
> Detected by CoveritScan, CID#1469407 ("Logically Dead code")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> sound/xen/xen_snd_front_evtchnl.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/sound/xen/xen_snd_front_evtchnl.c b/sound/xen/xen_snd_front_evtchnl.c
> index d70a62e7f910..102d6e096cc8 100644
> --- a/sound/xen/xen_snd_front_evtchnl.c
> +++ b/sound/xen/xen_snd_front_evtchnl.c
> @@ -351,8 +351,6 @@ int xen_snd_front_evtchnl_create_all(struct xen_snd_front_info *front_info,
> }
> }
> }
> - if (ret < 0)
> - goto fail;
>
> front_info->num_evt_pairs = num_streams;
> return 0;
Yep. All branches for error path on the nested for loop have goto
statement, thus no need to check error outer the loop.
Reviewed-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Takashi Sakamoto
next prev parent reply other threads:[~2018-05-27 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 21:23 Colin King
2018-05-27 22:42 ` Takashi Sakamoto [this message]
2018-05-28 9:29 ` Takashi Iwai
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=ee539e2d-568e-4bfa-a4aa-4a9b39bc1bd8@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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®