netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Yang Wei <albin_yang@163.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	kuznet@ms2.inr.ac.ru, yang.wei9@zte.com.cn
Subject: Re: [PATCH 1/2] net: fix coding style
Date: Thu, 24 Jan 2019 16:55:46 +0100	[thread overview]
Message-ID: <20190124155546.GE482@lunn.ch> (raw)
In-Reply-To: <1548340928-3768-1-git-send-email-albin_yang@163.com>

On Thu, Jan 24, 2019 at 10:42:08PM +0800, Yang Wei wrote:
Hi Yang

Your subject line needs to be a lot more specific.

Maybe something like:

net: ipv4: ip_input: Fix blank line coding style issues

> Fix coding style, remove redundant blank lines.

And this is also not accurate. You actually add a blank line.

    Andrew


> 
> Signed-off-by: Yang Wei <yang.wei9@zte.com.cn>
> ---
>  net/ipv4/ip_input.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/ipv4/ip_input.c b/net/ipv4/ip_input.c
> index 51d8efb..cd6b569 100644
> --- a/net/ipv4/ip_input.c
> +++ b/net/ipv4/ip_input.c
> @@ -429,7 +429,6 @@ static struct sk_buff *ip_rcv_core(struct sk_buff *skb, struct net *net)
>  	if (skb->pkt_type == PACKET_OTHERHOST)
>  		goto drop;
>  
> -
>  	__IP_UPD_PO_STATS(net, IPSTATS_MIB_IN, skb->len);
>  
>  	skb = skb_share_check(skb, GFP_ATOMIC);
> @@ -521,6 +520,7 @@ int ip_rcv(struct sk_buff *skb, struct net_device *dev, struct packet_type *pt,
>  	skb = ip_rcv_core(skb, net);
>  	if (skb == NULL)
>  		return NET_RX_DROP;
> +
>  	return NF_HOOK(NFPROTO_IPV4, NF_INET_PRE_ROUTING,
>  		       net, NULL, skb, dev, NULL,
>  		       ip_rcv_finish);
> -- 
> 2.7.4
> 
> 

      reply	other threads:[~2019-01-24 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 14:42 [PATCH 1/2] net: fix coding style Yang Wei
2019-01-24 15:55 ` Andrew Lunn [this message]

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=20190124155546.GE482@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=albin_yang@163.com \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=yang.wei9@zte.com.cn \
    /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).