From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wangyufen <wangyufen@huawei.com>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] ipv6: fix checkpatch errors of foo
Date: Tue, 25 Mar 2014 20:37:58 +0300 [thread overview]
Message-ID: <5331BEF6.5030900@cogentembedded.com> (raw)
In-Reply-To: <1395715493-5312-4-git-send-email-wangyufen@huawei.com>
Hello.
On 03/25/2014 05:44 AM, Wangyufen wrote:
> From: Wang Yufen <wangyufen@huawei.com>
> ERROR: "(foo*)" should be "(foo *)"
> ERROR: "foo * bar" should be "foo *bar"
> Signed-off-by: Wang Yufen <wangyufen@huawei.com>
> ---
> net/ipv6/ip6_fib.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
> diff --git a/net/ipv6/ip6_fib.c b/net/ipv6/ip6_fib.c
> index 8cb6949..22acde8 100644
> --- a/net/ipv6/ip6_fib.c
> +++ b/net/ipv6/ip6_fib.c
[...]
> @@ -951,7 +951,7 @@ struct lookup_args {
> const struct in6_addr *addr; /* search key */
> };
>
> -static struct fib6_node * fib6_lookup_1(struct fib6_node *root,
> +static struct fib6_node *fib6_lookup_1(struct fib6_node *root,
> struct lookup_args *args)
Reindent the above line please, so that it still starts under *struct* on
the previous line.
[...]
> @@ -1014,7 +1014,7 @@ backtrack:
> return NULL;
> }
>
> -struct fib6_node * fib6_lookup(struct fib6_node *root, const struct in6_addr *daddr,
> +struct fib6_node *fib6_lookup(struct fib6_node *root, const struct in6_addr *daddr,
> const struct in6_addr *saddr)
Likewise.
[...]
> @@ -1047,7 +1047,7 @@ struct fib6_node * fib6_lookup(struct fib6_node *root, const struct in6_addr *da
> */
>
>
> -static struct fib6_node * fib6_locate_1(struct fib6_node *root,
> +static struct fib6_node *fib6_locate_1(struct fib6_node *root,
> const struct in6_addr *addr,
> int plen, int offset)
Likewise.
[...]
> @@ -1077,7 +1077,7 @@ static struct fib6_node * fib6_locate_1(struct fib6_node *root,
> return NULL;
> }
>
> -struct fib6_node * fib6_locate(struct fib6_node *root,
> +struct fib6_node *fib6_locate(struct fib6_node *root,
> const struct in6_addr *daddr, int dst_len,
> const struct in6_addr *saddr, int src_len)
Likewise.
WBR, Sergei
prev parent reply other threads:[~2014-03-25 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 2:44 [PATCH net-next 0/3] ipv6: fix checkpatch errors and warnings Wangyufen
2014-03-25 2:44 ` [PATCH net-next 1/3] ipv6: fix checkpatch errors comments and space Wangyufen
2014-03-25 2:44 ` [PATCH net-next 2/3] ipv6: fix checkpatch errors of brace and trailing statements Wangyufen
2014-03-25 2:44 ` [PATCH net-next 3/3] ipv6: fix checkpatch errors of foo Wangyufen
2014-03-25 17:37 ` Sergei Shtylyov [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=5331BEF6.5030900@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=wangyufen@huawei.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 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.