From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][net-next] net: bridge: remove redundant check to see if err is set
Date: Tue, 07 Feb 2017 14:05:01 -0500 (EST) [thread overview]
Message-ID: <20170207.140501.318284472850132434.davem@davemloft.net> (raw)
In-Reply-To: <20170207105638.17918-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Tue, 7 Feb 2017 10:56:38 +0000
> From: Colin Ian King <colin.king@canonical.com>
>
> The error check on err is redundant as it is being checked
> previously each time it has been updated. Remove this redundant
> check.
>
> Detected with CoverityScan, CID#140030("Logically dead code")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied.
prev parent reply other threads:[~2017-02-07 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 10:56 [PATCH][net-next] net: bridge: remove redundant check to see if err is set Colin King
2017-02-07 11:30 ` Nikolay Aleksandrov
2017-02-07 11:43 ` Colin Ian King
2017-02-07 19:05 ` David Miller [this message]
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=20170207.140501.318284472850132434.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).