From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-s390@vger.kernel.org, linux-scsi@vger.kernel.org,
x86@kernel.org, linux-mips@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-crypto@vger.kernel.org, loongarch@lists.linux.dev,
sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-ext4@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [f2fs-dev] [PATCH v4 00/19] Wire up CRC32 library functions to arch-optimized code
Date: Wed, 29 Jan 2025 00:56:10 +0000 [thread overview]
Message-ID: <173811217076.3973351.8137382917166262630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241202010844.144356-1-ebiggers@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Eric Biggers <ebiggers@google.com>:
On Sun, 1 Dec 2024 17:08:25 -0800 you wrote:
> This patchset applies to v6.13-rc1 and is also available in git via:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git crc32-lib-v4
>
> CRC32 is a family of common non-cryptographic integrity check algorithms
> that are fairly fast with a portable C implementation and become far
> faster still with the CRC32 or carryless multiplication instructions
> that most CPUs have. 9 architectures already have optimized code for at
> least some CRC32 variants; however, except for arm64 this optimized code
> was only accessible through the crypto API, not the library functions.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v4,01/19] lib/crc32: drop leading underscores from __crc32c_le_base
https://git.kernel.org/jaegeuk/f2fs/c/0a499a7e9819
- [f2fs-dev,v4,02/19] lib/crc32: improve support for arch-specific overrides
https://git.kernel.org/jaegeuk/f2fs/c/d36cebe03c3a
- [f2fs-dev,v4,03/19] lib/crc32: expose whether the lib is really optimized at runtime
https://git.kernel.org/jaegeuk/f2fs/c/b5ae12e0ee09
- [f2fs-dev,v4,04/19] crypto: crc32 - don't unnecessarily register arch algorithms
https://git.kernel.org/jaegeuk/f2fs/c/780acb2543ea
- [f2fs-dev,v4,05/19] arm/crc32: expose CRC32 functions through lib
https://git.kernel.org/jaegeuk/f2fs/c/1e1b6dbc3d9c
- [f2fs-dev,v4,06/19] loongarch/crc32: expose CRC32 functions through lib
https://git.kernel.org/jaegeuk/f2fs/c/72f51a4f4b07
- [f2fs-dev,v4,07/19] mips/crc32: expose CRC32 functions through lib
https://git.kernel.org/jaegeuk/f2fs/c/289c270eab5e
- [f2fs-dev,v4,08/19] powerpc/crc32: expose CRC32 functions through lib
https://git.kernel.org/jaegeuk/f2fs/c/372ff60ac4dd
- [f2fs-dev,v4,09/19] s390/crc32: expose CRC32 functions through lib
https://git.kernel.org/jaegeuk/f2fs/c/008071917dfc
- [f2fs-dev,v4,10/19] sparc/crc32: expose CRC32 functions through lib
https://git.kernel.org/jaegeuk/f2fs/c/0f60a8ace577
- [f2fs-dev,v4,11/19] x86/crc32: update prototype for crc_pcl()
https://git.kernel.org/jaegeuk/f2fs/c/64e3586c0b61
- [f2fs-dev,v4,12/19] x86/crc32: update prototype for crc32_pclmul_le_16()
https://git.kernel.org/jaegeuk/f2fs/c/1e6b72e60a5a
- [f2fs-dev,v4,13/19] x86/crc32: expose CRC32 functions through lib
https://git.kernel.org/jaegeuk/f2fs/c/55d1ecceb8d6
- [f2fs-dev,v4,14/19] bcachefs: Explicitly select CRYPTO from BCACHEFS_FS
https://git.kernel.org/jaegeuk/f2fs/c/cc354fa7f016
- [f2fs-dev,v4,15/19] lib/crc32: make crc32c() go directly to lib
https://git.kernel.org/jaegeuk/f2fs/c/38a9a5121c3b
- [f2fs-dev,v4,16/19] ext4: switch to using the crc32c library
https://git.kernel.org/jaegeuk/f2fs/c/f2b4fa19647e
- [f2fs-dev,v4,17/19] jbd2: switch to using the crc32c library
https://git.kernel.org/jaegeuk/f2fs/c/dd348f054b24
- [f2fs-dev,v4,18/19] f2fs: switch to using the crc32 library
https://git.kernel.org/jaegeuk/f2fs/c/3ca4bec40ee2
- [f2fs-dev,v4,19/19] scsi: target: iscsi: switch to using the crc32c library
https://git.kernel.org/jaegeuk/f2fs/c/31e4cdde4d8b
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:[~2025-01-29 0:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 1:08 [PATCH v4 00/19] Wire up CRC32 library functions to arch-optimized code Eric Biggers
2024-12-02 1:08 ` [PATCH v4 01/19] lib/crc32: drop leading underscores from __crc32c_le_base Eric Biggers
2024-12-02 1:08 ` [PATCH v4 02/19] lib/crc32: improve support for arch-specific overrides Eric Biggers
2024-12-02 1:08 ` [PATCH v4 03/19] lib/crc32: expose whether the lib is really optimized at runtime Eric Biggers
2024-12-02 1:08 ` [PATCH v4 04/19] crypto: crc32 - don't unnecessarily register arch algorithms Eric Biggers
2024-12-02 1:08 ` [PATCH v4 05/19] arm/crc32: expose CRC32 functions through lib Eric Biggers
2024-12-02 1:08 ` [PATCH v4 06/19] loongarch/crc32: " Eric Biggers
2024-12-02 1:08 ` [PATCH v4 07/19] mips/crc32: " Eric Biggers
2024-12-02 1:08 ` [PATCH v4 08/19] powerpc/crc32: " Eric Biggers
2024-12-02 1:08 ` [PATCH v4 09/19] s390/crc32: " Eric Biggers
2024-12-02 1:08 ` [PATCH v4 10/19] sparc/crc32: " Eric Biggers
2024-12-02 1:08 ` [PATCH v4 11/19] x86/crc32: update prototype for crc_pcl() Eric Biggers
2024-12-02 1:08 ` [PATCH v4 12/19] x86/crc32: update prototype for crc32_pclmul_le_16() Eric Biggers
2024-12-02 1:08 ` [PATCH v4 13/19] x86/crc32: expose CRC32 functions through lib Eric Biggers
2024-12-02 1:08 ` [PATCH v4 14/19] bcachefs: Explicitly select CRYPTO from BCACHEFS_FS Eric Biggers
2024-12-02 1:08 ` [PATCH v4 15/19] lib/crc32: make crc32c() go directly to lib Eric Biggers
2024-12-02 1:08 ` [PATCH v4 16/19] ext4: switch to using the crc32c library Eric Biggers
2024-12-02 1:08 ` [PATCH v4 17/19] jbd2: " Eric Biggers
2024-12-02 1:08 ` [PATCH v4 18/19] f2fs: switch to using the crc32 library Eric Biggers
2024-12-02 1:08 ` [PATCH v4 19/19] scsi: target: iscsi: switch to using the crc32c library Eric Biggers
2024-12-12 21:37 ` [PATCH v4 00/19] Wire up CRC32 library functions to arch-optimized code Eric Biggers
2025-01-29 0:56 ` patchwork-bot+f2fs [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=173811217076.3973351.8137382917166262630.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=sparclinux@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).