From: David Miller <davem@davemloft.net>
To: dan.carpenter@oracle.com
Cc: linux-net-drivers@solarflare.com, ecree@solarflare.com,
bkenward@solarflare.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] sfc: cleanup a condition in efx_udp_tunnel_del()
Date: Wed, 22 Mar 2017 19:25:34 -0700 (PDT) [thread overview]
Message-ID: <20170322.192534.1032558291775882753.davem@davemloft.net> (raw)
In-Reply-To: <20170322091002.GB14520@mwanda>
From: Dan Carpenter <dan.carpenter@oracle.com>
Date: Wed, 22 Mar 2017 12:10:02 +0300
> Presumably if there is an "add" function, there is also a "del"
> function. But it causes a static checker warning because it looks like
> a common cut and paste bug.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Looks good, applied, thanks Dan.
prev parent reply other threads:[~2017-03-23 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 9:10 [patch] sfc: cleanup a condition in efx_udp_tunnel_del() Dan Carpenter
2017-03-22 21:41 ` Jarod Wilson
2017-03-23 2:25 ` 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=20170322.192534.1032558291775882753.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bkenward@solarflare.com \
--cc=dan.carpenter@oracle.com \
--cc=ecree@solarflare.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--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).