From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Subject: [PATCH net-next 05/12] be2net: remove return statements for void functions
Date: Fri, 19 Sep 2014 15:46:55 +0530 [thread overview]
Message-ID: <1411121822-25842-6-git-send-email-sathya.perla@emulex.com> (raw)
In-Reply-To: <1411121822-25842-1-git-send-email-sathya.perla@emulex.com>
From: Kalesh AP <kalesh.purayil@emulex.com>
Signed-off-by: Kalesh AP <kalesh.purayil@emulex.com>
Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
---
drivers/net/ethernet/emulex/benet/be_ethtool.c | 2 --
drivers/net/ethernet/emulex/benet/be_main.c | 3 ---
2 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ethernet/emulex/benet/be_ethtool.c b/drivers/net/ethernet/emulex/benet/be_ethtool.c
index ec66f64..32c61f3 100644
--- a/drivers/net/ethernet/emulex/benet/be_ethtool.c
+++ b/drivers/net/ethernet/emulex/benet/be_ethtool.c
@@ -975,8 +975,6 @@ static void be_set_msg_level(struct net_device *netdev, u32 level)
FW_LOG_LEVEL_DEFAULT :
FW_LOG_LEVEL_FATAL);
adapter->msg_enable = level;
-
- return;
}
static u64 be_get_rss_hash_opts(struct be_adapter *adapter, u64 flow_type)
diff --git a/drivers/net/ethernet/emulex/benet/be_main.c b/drivers/net/ethernet/emulex/benet/be_main.c
index beebab6..96be231 100644
--- a/drivers/net/ethernet/emulex/benet/be_main.c
+++ b/drivers/net/ethernet/emulex/benet/be_main.c
@@ -3716,8 +3716,6 @@ static void be_netpoll(struct net_device *netdev)
be_eq_notify(eqo->adapter, eqo->q.id, false, true, 0);
napi_schedule(&eqo->napi);
}
-
- return;
}
#endif
@@ -4395,7 +4393,6 @@ static void be_add_vxlan_port(struct net_device *netdev, sa_family_t sa_family,
return;
err:
be_disable_vxlan_offloads(adapter);
- return;
}
static void be_del_vxlan_port(struct net_device *netdev, sa_family_t sa_family,
--
1.7.1
next prev parent reply other threads:[~2014-09-19 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 10:16 [PATCH net-next 00/12] be2net: patch set Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 01/12] be2net: fix a sparse warning in be_cmd_modify_eqd() Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 02/12] be2net: fix sparse warnings in be_cmd_req_port_type{} Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 03/12] be2net: add speed reporting for 40G/KR interface Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 04/12] be2net: add speed reporting for 20G-KR interface Sathya Perla
2014-09-19 10:16 ` Sathya Perla [this message]
2014-09-19 10:16 ` [PATCH net-next 06/12] be2net: add blank line after declarations Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 07/12] be2net: remove multiple blank lines Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 08/12] be2net: insert a blank line after function/struct//enum definitions Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 09/12] be2net: remove unnecessary blank lines after an open brace Sathya Perla
2014-09-19 10:17 ` [PATCH net-next 10/12] be2net: remove space after typecasts Sathya Perla
2014-09-19 10:17 ` [PATCH net-next 11/12] be2net: remove multiple assignments on a single line Sathya Perla
2014-09-19 10:17 ` [PATCH net-next 12/12] be2net: fix alignment on line wrap Sathya Perla
2014-09-22 19:01 ` [PATCH net-next 00/12] be2net: patch set David Miller
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=1411121822-25842-6-git-send-email-sathya.perla@emulex.com \
--to=sathya.perla@emulex.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).