From: David Miller <davem@davemloft.net>
To: weiyj_lk@163.com
Cc: nicolas.dichtel@6wind.com, jin.xiao@intel.com,
viro@zeniv.linux.org.uk, ebiederm@xmission.com,
cwang@twopensource.com, edumazet@google.com,
yongjun_wei@trendmicro.com.cn, netdev@vger.kernel.org
Subject: Re: [PATCH -next] netns: remove duplicated include from net_namespace.c
Date: Thu, 16 Apr 2015 12:15:02 -0400 (EDT) [thread overview]
Message-ID: <20150416.121502.1759643517514397653.davem@davemloft.net> (raw)
In-Reply-To: <1429190255-24722-1-git-send-email-weiyj_lk@163.com>
From: weiyj_lk@163.com
Date: Thu, 16 Apr 2015 21:17:35 +0800
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> Remove duplicated include.
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Applied.
prev parent reply other threads:[~2015-04-16 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 13:17 [PATCH -next] netns: remove duplicated include from net_namespace.c weiyj_lk
2015-04-16 14:12 ` Nicolas Dichtel
2015-04-16 16:15 ` 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=20150416.121502.1759643517514397653.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cwang@twopensource.com \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=jin.xiao@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=viro@zeniv.linux.org.uk \
--cc=weiyj_lk@163.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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).