From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ian Morris <ipm@chirality.org.uk>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH nf-next 1/6] netfilter-ipv4: Line layout whitespace fixes
Date: Fri, 16 Oct 2015 19:22:26 +0200 [thread overview]
Message-ID: <20151016172226.GB3346@salvia> (raw)
In-Reply-To: <1444861028-21556-2-git-send-email-ipm@chirality.org.uk>
On Wed, Oct 14, 2015 at 11:17:03PM +0100, Ian Morris wrote:
> Cleanses some whitespace issues by removing a leading space before a tab.
>
> No changes detected by objdiff.
>
> Signed-off-by: Ian Morris <ipm@chirality.org.uk>
> ---
> net/ipv4/netfilter/ipt_ECN.c | 2 +-
> net/ipv4/netfilter/nf_nat_pptp.c | 2 +-
> net/ipv4/netfilter/nf_nat_snmp_basic.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/net/ipv4/netfilter/ipt_ECN.c b/net/ipv4/netfilter/ipt_ECN.c
> index 2707652..6592708 100644
> --- a/net/ipv4/netfilter/ipt_ECN.c
> +++ b/net/ipv4/netfilter/ipt_ECN.c
> @@ -24,7 +24,7 @@ MODULE_AUTHOR("Harald Welte <laforge@netfilter.org>");
> MODULE_DESCRIPTION("Xtables: Explicit Congestion Notification (ECN) flag modification");
>
> /* set ECT codepoint from IP header.
> - * return false if there was an error. */
> + * return false if there was an error. */
In netdev coding style we prefer for multiline comments:
/* This is a comment blah blah blah blah blah blah blah blah blah blah blah blah
* blah blah blah.
*/
For single line:
/* This is a comment blah blah blah */
This case, I suggest we can even get rid of that comment there since
it's obvious what set_ect_ip() is doing by reading the function name
and looking at what it returns.
next prev parent reply other threads:[~2015-10-16 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 22:17 [PATCH nf-next 0/6] coding style improvements: netfilter-ipv4 Ian Morris
2015-10-14 22:17 ` [PATCH nf-next 1/6] netfilter-ipv4: Line layout whitespace fixes Ian Morris
2015-10-16 17:22 ` Pablo Neira Ayuso [this message]
2015-10-14 22:17 ` [PATCH nf-next 2/6] netfilter-ipv4: label placement Ian Morris
2015-10-14 22:17 ` [PATCH nf-next 3/6] netfilter-ipv4: ternary operator layout Ian Morris
2015-10-14 22:17 ` [PATCH nf-next 4/6] netfilter-ipv4: function definition layout Ian Morris
2015-10-14 22:17 ` [PATCH nf-next 5/6] netfilter-ipv4: code indentation Ian Morris
2015-10-14 22:17 ` [PATCH nf-next 6/6] netfilter-ipv4: whitespace around operators Ian Morris
2015-10-16 17:20 ` [PATCH nf-next 0/6] coding style improvements: netfilter-ipv4 Pablo Neira Ayuso
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=20151016172226.GB3346@salvia \
--to=pablo@netfilter.org \
--cc=ipm@chirality.org.uk \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.