From: Fan Du <fan.du@windriver.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: David Miller <davem@davemloft.net>, <eric.dumazet@gmail.com>,
<xiyou.wangcong@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCHv4 net-next] xfrm: Namespacify xfrm_policy_sk_bundles
Date: Tue, 24 Dec 2013 17:56:37 +0800 [thread overview]
Message-ID: <52B95A55.2090207@windriver.com> (raw)
In-Reply-To: <20131224095007.GA29716@secunet.com>
On 2013年12月24日 17:50, Steffen Klassert wrote:
> On Tue, Dec 24, 2013 at 01:39:45PM +0800, Fan Du wrote:
>>
>>
>> On 2013年12月24日 13:31, David Miller wrote:
>>> From: Fan Du<fan.du@windriver.com>
>>> Date: Tue, 24 Dec 2013 09:12:32 +0800
>>>
>>>>> I saw this patch is marked 'Not Applicable' in patchwork.
>>> It means that it doesn't go in via my tree directly, it
>>> "doesn't apply".
>>>
>>> Instead, it goes into Steffen's IPSEC tree.
>>>
>
> Yes, I'll take care about this one. I'm currently traveling,
> so I have not that much time for review and tests of patches.
> I'll integrate all pending ipsec patches after the holidays.
>
>>
>> Thanks for your explanation!!!
>>
>> I'm not well understand the curtsy about patchwork, and one last question,
>> [PATCHv4 net-next 0/8] pktgen IPsec support is tagged as 'Awaiting Upstream'
>> what does that mean and do I need to take further action about this patch set?
>>
>
> I guess that means the same, it goes into the ipsec-next tree :)
Ok, I understood, and Merry Christmas!
--
浮沉随浪只记今朝笑
--fan
next prev parent reply other threads:[~2013-12-24 9:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 3:34 [PATCHv2 ipsec-next] xfrm: Namespacify xfrm_policy_sk_bundles Fan Du
2013-12-18 4:50 ` Eric Dumazet
2013-12-18 5:33 ` Cong Wang
2013-12-18 5:33 ` Fan Du
2013-12-18 5:44 ` Eric Dumazet
2013-12-19 1:35 ` Fan Du
2013-12-19 2:15 ` Eric Dumazet
2013-12-19 3:17 ` [PATCHv3 net-next] " Fan Du
2013-12-19 3:44 ` Eric Dumazet
2013-12-19 7:47 ` Fan Du
2013-12-20 3:34 ` [PATCHv4 " Fan Du
2013-12-24 1:12 ` Fan Du
2013-12-24 5:31 ` David Miller
2013-12-24 5:39 ` Fan Du
2013-12-24 9:50 ` Steffen Klassert
2013-12-24 9:56 ` Fan Du [this message]
2013-12-24 17:54 ` David Miller
2013-12-24 10:35 ` Steffen Klassert
2013-12-25 6:40 ` Fan Du
2013-12-25 8:11 ` Timo Teras
2013-12-25 8:44 ` Fan Du
2014-01-06 10:35 ` Steffen Klassert
2014-01-07 2:43 ` Fan Du
2014-01-09 12:38 ` Steffen Klassert
2014-01-10 9:23 ` Fan Du
2013-12-19 3:48 ` [PATCHv3 " Eric Dumazet
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=52B95A55.2090207@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=xiyou.wangcong@gmail.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).