From: chenweilong <chenweilong@huawei.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<netdev@vger.kernel.org>
Subject: Re: [patch net-next 2/5] xfrm: checkpatch errors with foo * bar
Date: Fri, 20 Dec 2013 16:54:14 +0800 [thread overview]
Message-ID: <52B405B6.4070407@huawei.com> (raw)
In-Reply-To: <20131220085029.GM31491@secunet.com>
On 2013/12/20 16:50, Steffen Klassert wrote:
> On Thu, Dec 19, 2013 at 08:22:11PM +0800, Chen Weilong wrote:
>> From: Weilong Chen <chenweilong@huawei.com>
>>
>> This patch clean up some checkpatch errors like this:
>> ERROR: "foo * bar" should be "foo *bar"
>> ERROR: "(foo*)" should be "(foo *)"
>>
>> Signed-off-by: Weilong Chen <chenweilong@huawei.com>
>
> This patch does not apply to the ipsec-next tree.
> Please rebase your patchset to ipsec-next and resend.
>
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
OK,I'll do that,Thanks!
next prev parent reply other threads:[~2013-12-20 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 12:22 [patch net-next 0/5] xfrm: fix checkpatch errors Chen Weilong
2013-12-19 12:22 ` [patch net-next 1/5] xfrm: checkpatch errors with space Chen Weilong
2013-12-19 12:22 ` [patch net-next 2/5] xfrm: checkpatch errors with foo * bar Chen Weilong
2013-12-20 8:50 ` Steffen Klassert
2013-12-20 8:54 ` chenweilong [this message]
2013-12-19 12:22 ` [patch net-next 3/5] xfrm: checkpatch erros with space prohibited Chen Weilong
2013-12-19 12:22 ` [patch net-next 4/5] xfrm: fix checkpatch error Chen Weilong
2013-12-19 12:22 ` [patch net-next 5/5] xfrm: checkpatch erros with inline keyword position Chen Weilong
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=52B405B6.4070407@huawei.com \
--to=chenweilong@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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.