From: "Arnd Bergmann" <arnd@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>, linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, "Ard Biesheuvel" <ardb@kernel.org>
Subject: Re: [PATCH v2] crypto: crc32 - remove "generic" from file and module names
Date: Mon, 28 Apr 2025 18:55:01 +0200 [thread overview]
Message-ID: <35c777f9-9767-48cf-acdb-9b47789f6c8b@app.fastmail.com> (raw)
In-Reply-To: <20250428162458.29732-1-ebiggers@kernel.org>
On Mon, Apr 28, 2025, at 18:24, Eric Biggers wrote:
>
> We could instead rename the library module to libcrc32.ko. However,
> while lib/crypto/ uses that convention, the rest of lib/ doesn't. Since
> the library API is the primary API for CRC-32, I'd like to keep the
> unsuffixed name for it and make the Crypto API modules use a suffix.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2025-04-28 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 16:24 Eric Biggers
2025-04-28 16:55 ` Arnd Bergmann [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=35c777f9-9767-48cf-acdb-9b47789f6c8b@app.fastmail.com \
--to=arnd@kernel.org \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®