From: Hongbin Wang <wh_bin@126.com>
To: davem@davemloft.net
Cc: yoshfuji@linux-ipv6.org, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH] seg6: Delete invalid code
Date: Thu, 29 Sep 2022 05:56:49 -0400 [thread overview]
Message-ID: <20220929095649.2764540-1-wh_bin@126.com> (raw)
void function return statements are not generally useful
Signed-off-by: Hongbin Wang <wh_bin@126.com>
---
net/ipv6/seg6_local.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/net/ipv6/seg6_local.c b/net/ipv6/seg6_local.c
index b7de5e46fdd8..a799ac83df3a 100644
--- a/net/ipv6/seg6_local.c
+++ b/net/ipv6/seg6_local.c
@@ -1830,8 +1830,6 @@ static void seg6_local_destroy_state(struct lwtunnel_state *lwt)
seg6_local_lwtunnel_destroy_state(slwt);
destroy_attrs(slwt);
-
- return;
}
static int seg6_local_fill_encap(struct sk_buff *skb,
--
2.25.1
next reply other threads:[~2022-09-29 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 9:56 Hongbin Wang [this message]
2022-09-30 1:25 ` [PATCH] seg6: Delete invalid code Jakub Kicinski
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=20220929095649.2764540-1-wh_bin@126.com \
--to=wh_bin@126.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).