From: patchwork-bot+netdevbpf@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ardb@kernel.org, Jason@zx2c4.com,
herbert@gondor.apana.org.au, 0x7f454c46@gmail.com
Subject: Re: [PATCH net-next 0/6] Remove unused support for crypto tfm cloning
Date: Fri, 29 May 2026 00:50:11 +0000 [thread overview]
Message-ID: <178001581139.1574269.16262378108123076484.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260522053028.91165-1-ebiggers@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 22 May 2026 00:30:22 -0500 you wrote:
> This series is targeting net-next because it depends on
> "net/tcp: Remove tcp_sigpool". So far no commits in cryptodev conflict
> with this, so I suggest that this be taken through net-next for 7.2.
>
> This series removes support for transformation cloning from the crypto
> API. Now that the TCP-AO and TCP-MD5 code no longer uses it, it no
> longer has a user. And it's unlikely that a new one will appear, as the
> library API solves the problem in a much simpler and more efficient way.
>
> [...]
Here is the summary with links:
- [net-next,1/6] crypto: hash - Remove support for cloning hash tfms
https://git.kernel.org/netdev/net-next/c/f331c7be97ce
- [net-next,2/6] crypto: cipher - Remove crypto_clone_cipher()
https://git.kernel.org/netdev/net-next/c/cb2e6e86ceb5
- [net-next,3/6] crypto: api - Remove crypto_clone_tfm()
https://git.kernel.org/netdev/net-next/c/590a46c68a7b
- [net-next,4/6] crypto: api - Remove per-tfm refcount
https://git.kernel.org/netdev/net-next/c/3065170bfc7f
- [net-next,5/6] crypto: api - Fold __crypto_alloc_tfmgfp() into __crypto_alloc_tfm()
https://git.kernel.org/netdev/net-next/c/9d58d14e3a18
- [net-next,6/6] crypto: api - Fold crypto_alloc_tfmmem() into crypto_create_tfm_node()
https://git.kernel.org/netdev/net-next/c/0200de9d75b1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-29 0:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 5:30 [PATCH net-next 0/6] Remove unused support for crypto tfm cloning Eric Biggers
2026-05-22 5:30 ` [PATCH net-next 1/6] crypto: hash - Remove support for cloning hash tfms Eric Biggers
2026-05-22 5:30 ` [PATCH net-next 2/6] crypto: cipher - Remove crypto_clone_cipher() Eric Biggers
2026-05-22 5:30 ` [PATCH net-next 3/6] crypto: api - Remove crypto_clone_tfm() Eric Biggers
2026-05-22 5:30 ` [PATCH net-next 4/6] crypto: api - Remove per-tfm refcount Eric Biggers
2026-05-22 5:30 ` [PATCH net-next 5/6] crypto: api - Fold __crypto_alloc_tfmgfp() into __crypto_alloc_tfm() Eric Biggers
2026-05-22 5:30 ` [PATCH net-next 6/6] crypto: api - Fold crypto_alloc_tfmmem() into crypto_create_tfm_node() Eric Biggers
2026-05-26 10:22 ` [PATCH net-next 0/6] Remove unused support for crypto tfm cloning Paolo Abeni
2026-05-28 23:23 ` Herbert Xu
2026-05-29 0:50 ` patchwork-bot+netdevbpf [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=178001581139.1574269.16262378108123076484.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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