From: Steffen Klassert <steffen.klassert@secunet•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patches in the ipsec-next tree
Date: Wed, 16 Apr 2025 10:48:15 +0200 [thread overview]
Message-ID: <Z/9uzypVKdsHwTCF@gauss3.secunet.de> (raw)
In-Reply-To: <20250415115000.08d2d16a@canb.auug.org.au>
On Tue, Apr 15, 2025 at 11:50:00AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the ipsec tree as different commits
> (but the same patches):
>
> ee2fc517feba ("espintcp: remove encap socket caching to avoid reference leak")
> 4f1d804e288e ("espintcp: fix skb leaks")
>
> These are commits
>
> 028363685bd0 ("espintcp: remove encap socket caching to avoid reference leak")
> 63c1f19a3be3 ("espintcp: fix skb leaks")
>
> in the ipsec tree.
They should have been just in the ipsec tree. I removed them from
ipsec-next. Sorry for this!
prev parent reply other threads:[~2025-04-16 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 1:50 linux-next: duplicate patches in the ipsec-next tree Stephen Rothwell
2025-04-16 8:48 ` 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=Z/9uzypVKdsHwTCF@gauss3.secunet.de \
--to=steffen.klassert@secunet$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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