From: Ying Xue <ying.xue@windriver.com>
To: Cong Wang <cwang@twopensource.com>
Cc: netdev <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Pavel Emelyanov <xemul@openvz.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [RFC PATCH v2 net-next] netlink: avoid namespace change while creating socket
Date: Fri, 8 May 2015 16:51:02 +0800 [thread overview]
Message-ID: <554C78F6.3040609@windriver.com> (raw)
In-Reply-To: <CAHA+R7MO9eKvbCd+jYf9U0Myr2dT0DXSZXiPq72AW+69n6+aag@mail.gmail.com>
On 05/08/2015 02:21 AM, Cong Wang wrote:
> On Thu, May 7, 2015 at 1:57 AM, Ying Xue <ying.xue@windriver.com> wrote:
>>
>> Thanks to Cong! Your below idea is absolutely better than mine.
>>
>> I have created a whole series based on the idea. Please review them.
>> In addition, I am not sure whether I should use your "Suggested-by" or
>> "Signed-off-by" tag in the first patch. But I finally selected the
>> "Suggested-by". If you think the tag is inappropriate, please let me know. I
>> will replace it with "Signed-off-by" tag in next version.
>>
>
> That is fairly easy to choose:
>
> If you use any code from me, you need my Signed-off-by.
> If you only get suggestion without any code, then Suggested-by.
>
>
OK, thanks for the clarification.
Regards,
Ying
prev parent reply other threads:[~2015-05-08 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 6:08 [RFC PATCH v2 net-next] netlink: avoid namespace change while creating socket Ying Xue
2015-05-06 23:03 ` Cong Wang
2015-05-07 8:57 ` Ying Xue
2015-05-07 18:21 ` Cong Wang
2015-05-08 8:51 ` Ying Xue [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=554C78F6.3040609@windriver.com \
--to=ying.xue@windriver.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.org \
/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).