From: Fengguang Wu <fengguang.wu@intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, lorenzo@google.com
Subject: Re: [PATCH net-next] net: ping_check_bind_addr() etc. can be static
Date: Wed, 12 Jun 2013 18:26:15 +0800 [thread overview]
Message-ID: <20130612102615.GB13837@localhost> (raw)
In-Reply-To: <20130612.011752.655896553563933294.davem@davemloft.net>
On Wed, Jun 12, 2013 at 01:17:52AM -0700, David Miller wrote:
> From: Fengguang Wu <fengguang.wu@intel.com>
> Date: Sun, 9 Jun 2013 20:24:26 +0800
>
> > /* Checks the bind address and possibly modifies sk->sk_bound_dev_if. */
> > -int ping_check_bind_addr(struct sock *sk, struct inet_sock *isk,
> > +static int ping_check_bind_addr(struct sock *sk, struct inet_sock *isk,
> > struct sockaddr *uaddr, int addr_len) {
>
> In all of these cases, you have to fix the indentation of all of the
> argument lines when the change the location of the openning
> parenthesis of the first line of the function definition.
>
> That's because in the networking we indent function declarations
> in the following way:
>
> int foo(int arg1, int arg2, int arg3,
> int arg4, int arg5)
>
> Specifically, the arguments that are declared on the second and
> subsequent lines must start at the first column after the openning
> parenthesis. This must be done using the appropriate number of
> TAB and space characters necessary to achieve that exact column.
>
> Please fix this up and combine your two patches into one.
OK I'll rework the patch, thank you for the kind tips!
Thanks,
Fengguang
next prev parent reply other threads:[~2013-06-12 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 12:24 [PATCH net-next] net: ping_check_bind_addr() etc. can be static Fengguang Wu
2013-06-09 12:28 ` [PATCH net-next] net: ipv6: ping_v6_seq_show() " Fengguang Wu
2013-06-12 8:17 ` [PATCH net-next] net: ping_check_bind_addr() etc. " David Miller
2013-06-12 10:26 ` Fengguang Wu [this message]
2013-06-12 13:04 ` [PATCH v2 " Fengguang Wu
2013-06-13 8:37 ` 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=20130612102615.GB13837@localhost \
--to=fengguang.wu@intel.com \
--cc=davem@davemloft.net \
--cc=lorenzo@google.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).