From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wangyufen <wangyufen@huawei.com>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 3/3] ipv6: fix checkpatch errors of "foo*" and "foo * bar"
Date: Fri, 28 Mar 2014 17:30:27 +0400 [thread overview]
Message-ID: <53357973.3010900@cogentembedded.com> (raw)
In-Reply-To: <1395979624-8544-4-git-send-email-wangyufen@huawei.com>
Hello.
On 28-03-2014 8:07, Wangyufen wrote:
> From: Wang Yufen <wangyufen@huawei.com>
> ERROR: "(foo*)" should be "(foo *)"
> ERROR: "foo * bar" should be "foo *bar"
>
> Suggested-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
I didn't really suggest to you to make this patch, I just commented on it.
You can instead add:
Acked-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Signed-off-by: Wang Yufen <wangyufen@huawei.com>
> ---
> net/ipv6/ip6_fib.c | 30 +++++++++++++++---------------
> 1 file changed, 15 insertions(+), 15 deletions(-)
WBR, Sergei
next prev parent reply other threads:[~2014-03-28 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 4:07 [PATCH net-next v2 0/3] ipv6: fix checkpatch errors and warnings Wangyufen
2014-03-28 4:07 ` [PATCH net-next v2 1/3] ipv6: fix checkpatch errors comments and space Wangyufen
2014-03-28 4:07 ` [PATCH net-next v2 2/3] ipv6: fix checkpatch errors of brace and trailing statements Wangyufen
2014-03-28 4:07 ` [PATCH net-next v2 3/3] ipv6: fix checkpatch errors of "foo*" and "foo * bar" Wangyufen
2014-03-28 4:22 ` Joe Perches
2014-03-28 5:40 ` David Miller
2014-03-28 5:47 ` Joe Perches
2014-03-28 9:33 ` wangyufen
2014-03-28 17:09 ` David Miller
2014-03-28 10:17 ` Hannes Frederic Sowa
2014-03-28 10:54 ` David Laight
2014-03-28 18:16 ` Hannes Frederic Sowa
2014-03-28 13:30 ` Sergei Shtylyov [this message]
2014-03-29 22:16 ` [PATCH net-next v2 0/3] ipv6: fix checkpatch errors and warnings 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=53357973.3010900@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 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).