netdev - Re: [PATCHv4 net-next] xfrm: Namespacify xfrm_policy_sk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52B95A55.2090207@windriver.com>
Date:	Tue, 24 Dec 2013 17:56:37 +0800
From:	Fan Du <fan.du@...driver.com>
To:	Steffen Klassert <steffen.klassert@...unet.com>
CC:	David Miller <davem@...emloft.net>, <eric.dumazet@...il.com>,
	<xiyou.wangcong@...il.com>, <netdev@...r.kernel.org>
Subject: Re: [PATCHv4 net-next] xfrm: Namespacify xfrm_policy_sk_bundles



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@...driver.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html