[<prev] [next>] [day] [month] [year] [list]
Message-ID: <aHSsUbP3JtdJtPfa@gauss3.secunet.de>
Date: Mon, 14 Jul 2025 09:05:53 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Aakash Kumar Shankarappa <saakashkumar@...vell.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
"davem@...emloft.net" <davem@...emloft.net>, "edumazet@...gle.com"
<edumazet@...gle.com>, "kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>, "horms@...nel.org"
<horms@...nel.org>, Abed Mohammad Kamaluddin <akamaluddin@...vell.com>,
"antony@...nome.org" <antony@...nome.org>
Subject: Re: [EXTERNAL] Re: [PATCH] xfrm: Duplicate SPI Handling
On Wed, Jul 09, 2025 at 10:20:42AM +0000, Aakash Kumar Shankarappa wrote:
> Hi Steffen,
> Thanks for applying the patch .
> Just to understand the flow better – will this go via your ipsec<https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git> tree for the next merge window or be queued for -net for stable ?
This was applied to the ipsec-next tree, it goes to
mainline during the next merge window. It will not
be backported to stable.
Powered by blists - more mailing lists