mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Silviu-Mihai Popescu <silviupopescu1990@gmail.com>
Cc: netdev@vger.kernel.org, sjur.brandeland@stericsson.com,
	davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CAIF: fix indentation for function arguments
Date: Wed, 06 Mar 2013 16:07:17 -0800	[thread overview]
Message-ID: <1362614837.2093.30.camel@joe-AO722> (raw)
In-Reply-To: <1362606521-16848-1-git-send-email-silviupopescu1990@gmail.com>

On Wed, 2013-03-06 at 23:48 +0200, Silviu-Mihai Popescu wrote:
> This lines up function arguments on second and subsequent lines at the
> first column after the openning parenthesis of the first line.
[]
> diff --git a/net/caif/caif_dev.c b/net/caif/caif_dev.c
[]
> @@ -301,10 +301,10 @@ static void dev_flowctrl(struct net_device *dev, int on)
>  }
>  
>  void caif_enroll_dev(struct net_device *dev, struct caif_dev_common *caifdev,
> -			struct cflayer *link_support, int head_room,
> -			struct cflayer **layer, int (**rcv_func)(
> -				struct sk_buff *, struct net_device *,
> -				struct packet_type *, struct net_device *))
> +		     struct cflayer *link_support, int head_room,
> +		     struct cflayer **layer, int (**rcv_func)(
> +		     struct sk_buff *, struct net_device *,
> +		     struct packet_type *, struct net_device *))

This makes it seem that caif_enroll_dev takes more args.

I think this style is better (aligned to appropriate open paren)

void caif_enroll_dev(struct net_device *dev, struct caif_dev_common *caifdev,
		     struct cflayer *link_support, int head_room,
		     struct cflayer **layer,
		     int (**rcv_func)(struct sk_buff *, struct net_device *,
				      struct packet_type *, struct net_device *))

[]

> @@ -301,8 +301,8 @@ static int caif_connect_req_to_link_param(struct cfcnfg *cnfg,
>  
>  int caif_connect_client(struct net *net, struct caif_connect_request *conn_req,
>  			struct cflayer *adap_layer, int *ifindex,
> -				int *proto_head,
> -				int *proto_tail)
> +			int *proto_head,
> +			int *proto_tail)

You could fill to 80 here.



  parent reply	other threads:[~2013-03-07  0:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 21:48 Silviu-Mihai Popescu
2013-03-06 22:36 ` Sjur Brændeland
2013-03-07  0:07 ` Joe Perches [this message]
2013-03-07  0:35   ` 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=1362614837.2093.30.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=silviupopescu1990@gmail.com \
    --cc=sjur.brandeland@stericsson.com \
    /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®