netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Mallon <rmallon@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/12] ping.h: Remove extern from function prototypes
Date: Mon, 23 Sep 2013 11:59:52 +1000	[thread overview]
Message-ID: <523FA098.9050200@gmail.com> (raw)
In-Reply-To: <b692aba58032f629907ea2d462c99b87906645ca.1379870986.git.joe@perches.com>

On 23/09/13 03:32, Joe Perches wrote:
> 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>

This seems like a lot of code churn for very little benefit. At a quick
glance:

  git grep extern include/ | wc -l
  11427

Not all of those will need to be removed, but that is still a huge
number to change, and doesn't include extern usage in C files or local
headers. You are probably never going to remove all the instances, so
what is the point of just randomly doing a handful?

~Ryan

> ---
>  include/net/ping.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/net/ping.h b/include/net/ping.h
> index 5db0224..3f67704 100644
> --- a/include/net/ping.h
> +++ b/include/net/ping.h
> @@ -103,8 +103,8 @@ void ping_seq_stop(struct seq_file *seq, void *v);
>  int ping_proc_register(struct net *net, struct ping_seq_afinfo *afinfo);
>  void ping_proc_unregister(struct net *net, struct ping_seq_afinfo *afinfo);
>  
> -extern int __init ping_proc_init(void);
> -extern void ping_proc_exit(void);
> +int __init ping_proc_init(void);
> +void ping_proc_exit(void);
>  #endif
>  
>  void __init ping_init(void);
> 

  parent reply	other threads:[~2013-09-23  1:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22 17:32 [PATCH 01/12] ping.h: Remove extern from function prototypes Joe Perches
2013-09-22 17:32 ` [PATCH 02/12] protocol.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 03/12] psnap.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 04/12] raw/rawv6.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 05/12] request_sock.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 06/12] rose.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 07/12] route.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 08/12] rtnetlink.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 09/12] scm.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 10/12] secure_seq.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 11/12] sock.h: " Joe Perches
2013-09-22 17:32 ` [PATCH 12/12] stp.h: " Joe Perches
2013-09-23  1:59 ` Ryan Mallon [this message]
2013-09-23  2:16   ` [PATCH 01/12] ping.h: " Joe Perches
2013-09-23  2:38     ` Ryan Mallon
2013-09-23  2:43       ` Joe Perches
2013-09-23  5:51 ` 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=523FA098.9050200@gmail.com \
    --to=rmallon@gmail.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --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;
as well as URLs for NNTP newsgroup(s).