From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: dhowells@redhat.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][net-next] rxrpc: remove redundant proc_remove call
Date: Sun, 04 Jun 2017 19:59:40 -0400 (EDT) [thread overview]
Message-ID: <20170604.195940.396015419684829733.davem@davemloft.net> (raw)
In-Reply-To: <20170602152227.3626-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Fri, 2 Jun 2017 16:22:27 +0100
> From: Colin Ian King <colin.king@canonical.com>
>
> The proc_remove call is dead code as it occurs after a return and
> hence can never be called. Remove it.
>
> Detected by CoverityScan, CID#1437743 ("Logically dead code")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied.
prev parent reply other threads:[~2017-06-04 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 15:22 Colin King
2017-06-02 21:37 ` David Howells
2017-06-04 23:59 ` 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=20170604.195940.396015419684829733.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colin.king@canonical.com \
--cc=dhowells@redhat.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
all inboxes | Powered by JetHome®