From: David Miller <davem@davemloft.net>
To: devtimhansen@gmail.com
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
alexander.levin@one.verizon.com
Subject: Re: [PATCH] net/ipv4: Remove unused variable in route.c
Date: Thu, 05 Oct 2017 21:17:05 -0700 (PDT) [thread overview]
Message-ID: <20171005.211705.976817989137040544.davem@davemloft.net> (raw)
In-Reply-To: <20171004195949.GA39492@debian>
From: Tim Hansen <devtimhansen@gmail.com>
Date: Wed, 4 Oct 2017 15:59:49 -0400
> int rc is unmodified after initalization in net/ipv4/route.c, this patch simply cleans up that variable and returns 0.
>
> This was found with coccicheck M=net/ipv4/ on linus' tree.
>
> Signed-off-by: Tim Hansen <devtimhansen@gmail.com>
Applied to net-next.
prev parent reply other threads:[~2017-10-06 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 19:59 [PATCH] net/ipv4: Remove unused variable in route.c Tim Hansen
2017-10-06 4:17 ` 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=20171005.211705.976817989137040544.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.levin@one.verizon.com \
--cc=devtimhansen@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).