From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Chao Yu <chao@kernel.org>, "Darrick J . Wong" <djwong@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Theodore Ts'o <tytso@mit.edu>,
Vinicius Peixoto <vpeixoto@lkcamp.dev>,
WangYuli <wangyuli@uniontech.com>
Subject: [PATCH 0/2] lib/crc: simplify choice of CRC implementations
Date: Thu, 23 Jan 2025 13:29:02 -0800 [thread overview]
Message-ID: <20250123212904.118683-1-ebiggers@kernel.org> (raw)
This series simplifies the choice of CRC implementations, as requested
by Linus at
https://lore.kernel.org/linux-crypto/CAHk-=wgqAZf7Sdyrka5RQQ2MVC1V_C1Gp68KrN=mHjPiRw70Jg@mail.gmail.com/
Eric Biggers (2):
lib/crc: simplify the kconfig options for CRC implementations
lib/crc32: remove other generic implementations
lib/Kconfig | 118 +++--------------------
lib/crc32.c | 225 ++-----------------------------------------
lib/crc32defs.h | 59 ------------
lib/gen_crc32table.c | 113 ++++++----------------
4 files changed, 53 insertions(+), 462 deletions(-)
delete mode 100644 lib/crc32defs.h
--
2.48.1
next reply other threads:[~2025-01-23 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 21:29 Eric Biggers [this message]
2025-01-23 21:29 ` [PATCH 1/2] lib/crc: simplify the kconfig options for CRC implementations Eric Biggers
2025-01-23 21:29 ` [PATCH 2/2] lib/crc32: remove other generic implementations Eric Biggers
2025-01-25 11:14 ` David Laight
2025-01-25 0:37 ` [PATCH 0/2] lib/crc: simplify choice of CRC implementations Eric Biggers
2025-01-29 16:11 ` Ard Biesheuvel
2025-01-29 3:00 ` Martin K. Petersen
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=20250123212904.118683-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=geert@linux-m68k.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vpeixoto@lkcamp.dev \
--cc=wangyuli@uniontech.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;
as well as URLs for NNTP newsgroup(s).