Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/3] crypto: Remove cavium zip and drop scomp dst buffer
Date: Wed, 19 Mar 2025 20:31:42 +0800	[thread overview]
Message-ID: <cover.1742387288.git.herbert@gondor.apana.org.au> (raw)

This series removes the cavium zip driver and the dst scratch buffer
from scomp.  The latter could use up to 64K of memory per CPU.

Herbert Xu (3):
  crypto: cavium - Move cpt and nitrox rules into cavium Makefile
  crypto: cavium/zip - Remove driver
  crypto: scomp - Drop the dst scratch buffer

 crypto/scompress.c                      |   98 +-
 drivers/crypto/Kconfig                  |    7 -
 drivers/crypto/Makefile                 |    4 +-
 drivers/crypto/cavium/Makefile          |    3 +-
 drivers/crypto/cavium/zip/Makefile      |   12 -
 drivers/crypto/cavium/zip/common.h      |  222 ----
 drivers/crypto/cavium/zip/zip_crypto.c  |  261 -----
 drivers/crypto/cavium/zip/zip_crypto.h  |   68 --
 drivers/crypto/cavium/zip/zip_deflate.c |  200 ----
 drivers/crypto/cavium/zip/zip_deflate.h |   62 --
 drivers/crypto/cavium/zip/zip_device.c  |  202 ----
 drivers/crypto/cavium/zip/zip_device.h  |  108 --
 drivers/crypto/cavium/zip/zip_inflate.c |  223 ----
 drivers/crypto/cavium/zip/zip_inflate.h |   62 --
 drivers/crypto/cavium/zip/zip_main.c    |  603 ----------
 drivers/crypto/cavium/zip/zip_main.h    |  120 --
 drivers/crypto/cavium/zip/zip_mem.c     |  114 --
 drivers/crypto/cavium/zip/zip_mem.h     |   78 --
 drivers/crypto/cavium/zip/zip_regs.h    | 1347 -----------------------
 19 files changed, 47 insertions(+), 3747 deletions(-)
 delete mode 100644 drivers/crypto/cavium/zip/Makefile
 delete mode 100644 drivers/crypto/cavium/zip/common.h
 delete mode 100644 drivers/crypto/cavium/zip/zip_crypto.c
 delete mode 100644 drivers/crypto/cavium/zip/zip_crypto.h
 delete mode 100644 drivers/crypto/cavium/zip/zip_deflate.c
 delete mode 100644 drivers/crypto/cavium/zip/zip_deflate.h
 delete mode 100644 drivers/crypto/cavium/zip/zip_device.c
 delete mode 100644 drivers/crypto/cavium/zip/zip_device.h
 delete mode 100644 drivers/crypto/cavium/zip/zip_inflate.c
 delete mode 100644 drivers/crypto/cavium/zip/zip_inflate.h
 delete mode 100644 drivers/crypto/cavium/zip/zip_main.c
 delete mode 100644 drivers/crypto/cavium/zip/zip_main.h
 delete mode 100644 drivers/crypto/cavium/zip/zip_mem.c
 delete mode 100644 drivers/crypto/cavium/zip/zip_mem.h
 delete mode 100644 drivers/crypto/cavium/zip/zip_regs.h

-- 
2.39.5


             reply	other threads:[~2025-03-19 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 12:31 Herbert Xu [this message]
2025-03-19 12:31 ` [PATCH 1/3] crypto: cavium - Move cpt and nitrox rules into cavium Makefile Herbert Xu
2025-03-19 12:31 ` [PATCH 2/3] crypto: cavium/zip - Remove driver Herbert Xu
2025-03-19 12:31 ` [PATCH 3/3] crypto: scomp - Drop the dst scratch buffer Herbert Xu
2025-03-20  7:49 ` [PATCH 0/3] crypto: Remove cavium zip and drop scomp dst buffer Ard Biesheuvel

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=cover.1742387288.git.herbert@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=ardb@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    /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