From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] lib/crc: Drop inline from all *_mod_init_arch() functions
Date: Wed, 20 Aug 2025 23:37:34 -0400 [thread overview]
Message-ID: <20250821033734.GD185832@quark> (raw)
In-Reply-To: <20250816020240.431545-1-ebiggers@kernel.org>
On Fri, Aug 15, 2025 at 07:02:40PM -0700, Eric Biggers wrote:
> Drop 'inline' from all the *_mod_init_arch() functions so that the
> compiler will warn about any bugs where they are unused due to not being
> wired up properly. (There are no such bugs currently, so this just
> establishes a more robust convention for the future. Of course, these
> functions also tend to get inlined anyway, regardless of the keyword.)
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> lib/crc/arm/crc-t10dif.h | 2 +-
> lib/crc/arm/crc32.h | 2 +-
> lib/crc/arm64/crc-t10dif.h | 2 +-
> lib/crc/loongarch/crc32.h | 2 +-
> lib/crc/mips/crc32.h | 2 +-
> lib/crc/powerpc/crc-t10dif.h | 2 +-
> lib/crc/powerpc/crc32.h | 2 +-
> lib/crc/sparc/crc32.h | 2 +-
> lib/crc/x86/crc-t10dif.h | 2 +-
> lib/crc/x86/crc32.h | 2 +-
> lib/crc/x86/crc64.h | 2 +-
> 11 files changed, 11 insertions(+), 11 deletions(-)
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next
- Eric
prev parent reply other threads:[~2025-08-21 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 2:02 [PATCH] lib/crc: Drop inline from all *_mod_init_arch() functions Eric Biggers
2025-08-21 3:37 ` Eric Biggers [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=20250821033734.GD185832@quark \
--to=ebiggers@kernel.org \
--cc=ardb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.