From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: bridge@lists.linux-foundation.org, bart.de.schuymer@pandora.be,
tanxiaojun@huawei.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] bridge: cleanup and fix checkpatch errors
Date: Thu, 19 Dec 2013 19:28:20 -0500 (EST) [thread overview]
Message-ID: <20131219.192820.29526772886243119.davem@davemloft.net> (raw)
In-Reply-To: <20131219104112.3fcdbf8a@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 19 Dec 2013 10:41:12 -0800
> On Thu, 19 Dec 2013 13:28:09 +0800
> Tan Xiaojun <tanxiaojun@huawei.com> wrote:
>
>> Clean up and fix some checkpatch errors in bridge driver.
>>
>> Tan Xiaojun (5):
>> bridge: remove unnecessary condition judgment
>> bridge: remove unnecessary parentheses
>> bridge: add space before '(/{', after ',', etc.
>> bridge: change "foo* bar" to "foo *bar"
>> bridge: change the position of '{' to the pre line
...
>
> Thanks, these should go to net-next.
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Series applied, thanks.
prev parent reply other threads:[~2013-12-20 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 5:28 [PATCH 0/5] bridge: cleanup and fix checkpatch errors Tan Xiaojun
2013-12-19 5:28 ` [PATCH 1/5] bridge: remove unnecessary condition judgment Tan Xiaojun
2013-12-19 5:28 ` [PATCH 2/5] bridge: remove unnecessary parentheses Tan Xiaojun
2013-12-19 5:28 ` [PATCH 3/5] bridge: add space before '(/{', after ',', etc Tan Xiaojun
2013-12-19 5:28 ` [PATCH 4/5] bridge: change "foo* bar" to "foo *bar" Tan Xiaojun
2013-12-19 5:28 ` [PATCH 5/5] bridge: change the position of '{' to the pre line Tan Xiaojun
2013-12-19 6:59 ` [PATCH 0/5] bridge: cleanup and fix checkpatch errors Tan Xiaojun
2013-12-19 18:41 ` Stephen Hemminger
2013-12-20 0:28 ` David Miller [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=20131219.192820.29526772886243119.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bart.de.schuymer@pandora.be \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tanxiaojun@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).