From: Steffen Klassert <steffen.klassert@secunet.com>
To: Aakash Kumar Shankarappa <saakashkumar@marvell.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
Abed Mohammad Kamaluddin <akamaluddin@marvell.com>,
"antony@phenome.org" <antony@phenome.org>
Subject: Re: [EXTERNAL] Re: [PATCH] xfrm: Duplicate SPI Handling
Date: Mon, 14 Jul 2025 09:05:53 +0200 [thread overview]
Message-ID: <aHSsUbP3JtdJtPfa@gauss3.secunet.de> (raw)
In-Reply-To: <BL1PPF236BDCF3E6140C103E6AA14EE5FF0DA49A@BL1PPF236BDCF3E.namprd18.prod.outlook.com>
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.
prev parent reply other threads:[~2025-07-14 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 12:38 [PATCH] xfrm: Duplicate SPI Handling Aakash Kumar S
2025-07-04 7:33 ` Steffen Klassert
[not found] ` <BL1PPF236BDCF3E6140C103E6AA14EE5FF0DA49A@BL1PPF236BDCF3E.namprd18.prod.outlook.com>
2025-07-14 7:05 ` Steffen Klassert [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=aHSsUbP3JtdJtPfa@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=akamaluddin@marvell.com \
--cc=antony@phenome.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saakashkumar@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.