Netdev List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	David Miller <davem@davemloft.net>,
	YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
	Vasiliy Kulikov <segoon@openwall.com>
Subject: Re: [PATCH v4 1/4] Clean up indentation in net/ipv6/transp_v6.h
Date: Fri, 31 May 2013 18:25:40 -0700	[thread overview]
Message-ID: <1370049940.10556.100.camel@joe-AO722> (raw)
In-Reply-To: <1370048750-28441-1-git-send-email-lorenzo@google.com>

On Sat, 2013-06-01 at 10:05 +0900, Lorenzo Colitti wrote:
> Reduce the indentation of most of the functions and make it a
> bit more consistent. This allows longer function and arg names
> to be consistently indented without wrapping.
[]
> diff --git a/include/net/transp_v6.h b/include/net/transp_v6.h
[]
> @@ -7,47 +7,47 @@
[]
>  /* extension headers */
> -extern int				ipv6_exthdrs_init(void);
[]
> +extern int		ipv6_exthdrs_init(void);

externs aren't useful here and I suggest prototypes like
int ipv6_exthdrs_init(void);

> -extern int			ip6_datagram_send_ctl(struct net *net,
> -						      struct sock *sk,
> -						      struct msghdr *msg,
> -						      struct flowi6 *fl6,
> -						      struct ipv6_txoptions *opt,
> -						      int *hlimit, int *tclass,
> -						      int *dontfrag);
[]
> +extern int		ip6_datagram_send_ctl(struct net *net,
> +					      struct sock *sk,
> +					      struct msghdr *msg,
> +					      struct flowi6 *fl6,
> +					      struct ipv6_txoptions *opt,
> +					      int *hlimit, int *tclass,
> +					      int *dontfrag);

int ip6_datagram_send_ctl(struct net *net, struct sock *sk, struct msghdr *msg,
			  struct flowi6 *fl6, struct ipv6_txoptions *opt,
			  int *hlimit, int *tclass, int *dontfrag);

etc...

kernel_doc might be nice too

  parent reply	other threads:[~2013-06-01  1:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  1:05 [PATCH v4 1/4] Clean up indentation in net/ipv6/transp_v6.h Lorenzo Colitti
2013-06-01  1:05 ` [PATCH v4 2/4] net: ipv6: Unify {raw,udp}6_sock_seq_show Lorenzo Colitti
2013-06-04 19:56   ` David Miller
2013-06-01  1:05 ` [PATCH v4 3/4] net: ipv4: make the ping /proc code AF-independent Lorenzo Colitti
2013-06-04 19:57   ` David Miller
2013-06-01  1:05 ` [PATCH v4 4/4] net: ipv6: Implement /proc/net/icmp6 Lorenzo Colitti
2013-06-04 19:57   ` David Miller
2013-06-01  1:25 ` Joe Perches [this message]
2013-06-02  2:58   ` [PATCH v4 1/4] Clean up indentation in net/ipv6/transp_v6.h David Miller
2013-06-02  3:06     ` Joe Perches
2013-06-02  3:44       ` Lorenzo Colitti
2013-06-02  3:52         ` Joe Perches
2013-06-02  8:29       ` David Miller
2013-06-02  9:23         ` Joe Perches
2013-06-02 10:35           ` Lorenzo Colitti
2013-06-02 17:04             ` [PATCH net-next post Lorenzo] transp_v6.h: style neatening Joe Perches
2013-06-03  2:20               ` Lorenzo Colitti
2013-06-03  2:34                 ` Joe Perches
2013-06-02 14:16           ` [PATCH v4 1/4] Clean up indentation in net/ipv6/transp_v6.h Eric Dumazet
2013-06-02 17:30             ` Joe Perches
2013-06-04 19: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=1370049940.10556.100.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=lorenzo@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=segoon@openwall.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