Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
	dhowells@redhat.com, marc.dionne@auristor.com,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net-next v2 0/5] Consolidate FCrypt and PCBC code into net/rxrpc/
Date: Wed, 10 Jun 2026 00:20:09 +0000	[thread overview]
Message-ID: <178105080939.2761032.9825918956605127872.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260522050740.84561-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:07:31 -0500 you wrote:
> The FCrypt "block cipher" and the PCBC mode of operation are obsolete
> and insecure.  Since their only user is net/rxrpc/, they belong there,
> not in the crypto API.
> 
> Therefore, this series removes these algorithms from the crypto API and
> replaces them with local implementations in net/rxrpc/.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/5] net/rxrpc: Add local FCrypt-PCBC implementation
    https://git.kernel.org/netdev/net-next/c/f10e73dffd2a
  - [net-next,v2,2/5] net/rxrpc: Use local FCrypt-PCBC implementation
    https://git.kernel.org/netdev/net-next/c/97b768514a6e
  - [net-next,v2,3/5] net/rxrpc: Reimplement DES-PCBC using DES library
    https://git.kernel.org/netdev/net-next/c/432042e25e33
  - [net-next,v2,4/5] crypto: fcrypt - Remove support for FCrypt block cipher
    https://git.kernel.org/netdev/net-next/c/374efbdc85d0
  - [net-next,v2,5/5] crypto: pcbc - Remove support for PCBC mode
    https://git.kernel.org/netdev/net-next/c/1967bfaf7ba1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-06-10  0:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22  5:07 [PATCH net-next v2 0/5] Consolidate FCrypt and PCBC code into net/rxrpc/ Eric Biggers
2026-05-22  5:07 ` [PATCH net-next v2 1/5] net/rxrpc: Add local FCrypt-PCBC implementation Eric Biggers
2026-05-22  5:07 ` [PATCH net-next v2 2/5] net/rxrpc: Use " Eric Biggers
2026-05-22  5:07 ` [PATCH net-next v2 3/5] net/rxrpc: Reimplement DES-PCBC using DES library Eric Biggers
2026-05-22  5:07 ` [PATCH net-next v2 4/5] crypto: fcrypt - Remove support for FCrypt block cipher Eric Biggers
2026-05-22  5:07 ` [PATCH net-next v2 5/5] crypto: pcbc - Remove support for PCBC mode Eric Biggers
2026-05-22 13:06 ` [PATCH net-next v2 0/5] Consolidate FCrypt and PCBC code into net/rxrpc/ Marc Dionne
2026-06-03  5:05   ` Eric Biggers
2026-06-08 17:39     ` Eric Biggers
2026-06-08 18:11       ` Marc Dionne
2026-06-09  6:18       ` David Howells
2026-06-09 16:11         ` Paolo Abeni
2026-06-10  2:38           ` Herbert Xu
2026-06-10  0:20 ` 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=178105080939.2761032.9825918956605127872.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.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