public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	Demian Shulhan <demyansh@gmail.com>
Subject: [GIT PULL] CRC updates for 7.1
Date: Sat, 11 Apr 2026 17:23:43 -0700	[thread overview]
Message-ID: <20260412002343.GB6632@sol> (raw)

The following changes since commit 1f318b96cc84d7c2ab792fcc0bfd42a7ca890681:

  Linux 7.0-rc3 (2026-03-08 16:56:54 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git tags/crc-for-linus

for you to fetch changes up to 8fdef85d601db670e9c178314eedffe7bbb07e52:

  lib/crc: arm64: Simplify intrinsics implementation (2026-04-02 16:14:53 -0700)

----------------------------------------------------------------

- Several improvements related to crc_kunit, to align with the
  standard KUnit conventions and make it easier for developers and CI
  systems to run this test suite

- Add an arm64-optimized implementation of CRC64-NVME

- Remove unused code for big endian arm64

----------------------------------------------------------------
Ard Biesheuvel (3):
      lib/crc: arm64: Drop unnecessary chunking logic from crc64
      lib/crc: arm64: Use existing macros for kernel-mode FPU cflags
      lib/crc: arm64: Simplify intrinsics implementation

Demian Shulhan (1):
      lib/crc: arm64: add NEON accelerated CRC64-NVMe implementation

Eric Biggers (8):
      lib/crc: tests: Make crc_kunit test only the enabled CRC variants
      lib/crc: tests: Add CRC_ENABLE_ALL_FOR_KUNIT
      lib/crc: tests: Add a .kunitconfig file
      kunit: configs: Enable all CRC tests in all_tests.config
      crypto: crc32c - Remove more outdated usage information
      crypto: crc32c - Remove another outdated comment
      lib/crc: arm64: Drop check for CONFIG_KERNEL_MODE_NEON
      lib/crc: arm64: Assume a little-endian kernel

 crypto/crc32c.c                              | 19 +-------
 lib/crc/.kunitconfig                         |  3 ++
 lib/crc/Kconfig                              | 20 ++++++---
 lib/crc/Makefile                             |  7 ++-
 lib/crc/arm64/crc-t10dif-core.S              | 56 ++++++++++++------------
 lib/crc/arm64/crc32-core.S                   |  9 +---
 lib/crc/arm64/crc64-neon-inner.c             | 65 ++++++++++++++++++++++++++++
 lib/crc/arm64/crc64.h                        | 28 ++++++++++++
 lib/crc/tests/crc_kunit.c                    | 28 +++++++++---
 tools/testing/kunit/configs/all_tests.config |  2 +
 10 files changed, 172 insertions(+), 65 deletions(-)
 create mode 100644 lib/crc/.kunitconfig
 create mode 100644 lib/crc/arm64/crc64-neon-inner.c
 create mode 100644 lib/crc/arm64/crc64.h

                 reply	other threads:[~2026-04-12  0:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260412002343.GB6632@sol \
    --to=ebiggers@kernel.org \
    --cc=ardb@kernel.org \
    --cc=demyansh@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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