mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: [PATCH 08/11] garp.h: Remove extern from function prototypes
Date: Fri, 20 Sep 2013 11:23:25 -0700	[thread overview]
Message-ID: <ac245c0f23dd6f797457718cfcb602a9efd43728.1379701322.git.joe@perches.com> (raw)
In-Reply-To: <597c1b62607f823af60dc4a99d59373dddfb7837.1379701322.git.joe@perches.com>

There are a mix of function prototypes with and without extern
in the kernel sources.  Standardize on not using extern for
function prototypes.

Function prototypes don't need to be written with extern.
extern is assumed by the compiler.  Its use is as unnecessary as
using auto to declare automatic/local variables in a block.

Signed-off-by: Joe Perches <joe@perches.com>
---
 include/net/garp.h | 27 +++++++++++++--------------
 1 file changed, 13 insertions(+), 14 deletions(-)

diff --git a/include/net/garp.h b/include/net/garp.h
index 834d8ad..abf33bb 100644
--- a/include/net/garp.h
+++ b/include/net/garp.h
@@ -112,19 +112,18 @@ struct garp_port {
 	struct rcu_head			rcu;
 };
 
-extern int	garp_register_application(struct garp_application *app);
-extern void	garp_unregister_application(struct garp_application *app);
-
-extern int	garp_init_applicant(struct net_device *dev,
-				    struct garp_application *app);
-extern void	garp_uninit_applicant(struct net_device *dev,
-				      struct garp_application *app);
-
-extern int	garp_request_join(const struct net_device *dev,
-				  const struct garp_application *app,
-				  const void *data, u8 len, u8 type);
-extern void	garp_request_leave(const struct net_device *dev,
-				   const struct garp_application *app,
-				   const void *data, u8 len, u8 type);
+int garp_register_application(struct garp_application *app);
+void garp_unregister_application(struct garp_application *app);
+
+int garp_init_applicant(struct net_device *dev, struct garp_application *app);
+void garp_uninit_applicant(struct net_device *dev,
+			   struct garp_application *app);
+
+int garp_request_join(const struct net_device *dev,
+		      const struct garp_application *app, const void *data,
+		      u8 len, u8 type);
+void garp_request_leave(const struct net_device *dev,
+			const struct garp_application *app,
+			const void *data, u8 len, u8 type);
 
 #endif /* _NET_GARP_H */
-- 
1.8.1.2.459.gbcd45b4.dirty


  parent reply	other threads:[~2013-09-20 18:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 18:23 [PATCH 01/11] compat.h: " Joe Perches
2013-09-20 18:23 ` [PATCH 02/11] dcbevent.h: " Joe Perches
2013-09-20 18:23 ` [PATCH 03/11] decnet (dn*.h): " Joe Perches
2013-09-20 18:23 ` [PATCH 04/11] dst.h: " Joe Perches
2013-09-20 18:23 ` [PATCH 05/11] esp.h: " Joe Perches
2013-09-20 18:23 ` [PATCH 06/11] fib_rules.h: " Joe Perches
2013-09-20 18:23 ` [PATCH 07/11] flow.h/flow_keys.h: " Joe Perches
2013-09-20 18:23 ` Joe Perches [this message]
2013-09-20 18:23 ` [PATCH 09/11] gen_stats.h: " Joe Perches
2013-09-20 18:23 ` [PATCH 10/11] genetlink.h: " Joe Perches
2013-09-20 18:23 ` [PATCH 11/11] icmp.h: " Joe Perches
2013-09-20 18:49 ` [PATCH 01/11] compat.h: " David Miller
2013-09-20 18:53   ` Joe Perches
2013-09-20 18:56     ` 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=ac245c0f23dd6f797457718cfcb602a9efd43728.1379701322.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --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®