From: David Miller <davem@davemloft.net>
To: saurabh.mohan@vyatta.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next PATCH 02/02] net/ipv4: VTI support new module for ip_vti.
Date: Thu, 28 Jun 2012 18:07:25 -0700 (PDT) [thread overview]
Message-ID: <20120628.180725.2244572424738509573.davem@davemloft.net> (raw)
In-Reply-To: <20120629005231.GA4511@debian-saurabh-64.vyatta.com>
From: Saurabh <saurabh.mohan@vyatta.com>
Date: Thu, 28 Jun 2012 17:52:31 -0700
> +static struct rtnl_link_stats64 *vti_get_stats64(struct net_device *dev,
> + struct rtnl_link_stats64 *tot)
Imporperly indentex, all of the argument lines must line up with the first
column after the initial "(" on the first line.
> +static struct ip_tunnel *vti_tunnel_lookup(struct net *net,
> + __be32 remote, __be32 local)
Likewise.
> +static struct ip_tunnel **__vti_bucket(struct vti_net *ipn,
> + struct ip_tunnel_parm *parms)
Likewise.
> +static inline struct ip_tunnel **vti_bucket(struct vti_net *ipn,
> + struct ip_tunnel *t)
Likewise.
> +static struct ip_tunnel *vti_tunnel_locate(struct net *net,
> + struct ip_tunnel_parm *parms,
> + int create)
Likewise.
> + for (tp = __vti_bucket(ipn, parms);
> + (t = rtnl_dereference(*tp)) != NULL;
> + tp = &t->next) {
I find it very amusing that you are able to format this for() statement
correctly, but in the entire patch #1 you were unable to. It's like
this patch was written by a completely different person.
> + rcu_read_lock();
> + t = vti_tunnel_lookup(dev_net(skb->dev), iph->daddr, iph->saddr);
> + if (t == NULL)
> + goto out;
You should return -ENOENT, like ipip() does, when the tunnel cannot
be found.
> + flowi4_init_output(&fl4, tunnel->parms.link,
> + htonl(tunnel->parms.i_key), RT_TOS(tos), RT_SCOPE_UNIVERSE,
> + IPPROTO_IPIP, 0,
> + dst, tiph->saddr, 0, 0);
Indent these arguments properly.
> + /*
> + * if there is no transform then this tunnel is not functional.
> + * Or if the xfrm is not mode tunnel.
> + */
Format comments:
/* Like
* this.
*/
Not:
/*
* Like
* this.
*/
> + flowi4_init_output(&fl4, tunnel->parms.link,
> + htonl(tunnel->parms.i_key), RT_TOS(iph->tos), RT_SCOPE_UNIVERSE,
> + IPPROTO_IPIP, 0,
> + iph->daddr, iph->saddr, 0, 0);
Fix this indentation.
next prev parent reply other threads:[~2012-06-29 1:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 0:52 [net-next PATCH 02/02] net/ipv4: VTI support new module for ip_vti Saurabh
2012-06-29 1:07 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-17 19:44 Saurabh
2012-06-29 1:30 Saurabh
2012-07-09 6:47 ` David Miller
2012-06-28 1:02 Saurabh
2012-06-28 1:19 ` David Miller
2012-06-28 8:04 ` Steffen Klassert
2012-06-08 17:32 Saurabh
2012-06-14 9:12 ` Steffen Klassert
2012-06-15 2:43 ` Saurabh Mohan
2012-06-15 3:50 ` David Miller
2012-06-15 5:37 ` Steffen Klassert
2012-06-16 1:12 ` Saurabh Mohan
2012-06-17 23:27 ` 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=20120628.180725.2244572424738509573.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=saurabh.mohan@vyatta.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;
as well as URLs for NNTP newsgroup(s).