public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-crypto@vger.kernel.org,
	Heiko Carstens <hca@linux.ibm.com>
Subject: [PATCH] s390/crc32: Remove no-op module init and exit functions
Date: Thu, 17 Apr 2025 09:38:29 -0700	[thread overview]
Message-ID: <20250417163829.4599-1-ebiggers@kernel.org> (raw)

From: Eric Biggers <ebiggers@google.com>

Now that the crc32-s390 module init function is a no-op, there is no
need to define it.  Remove it.  The removal of the init function also
makes the exit function unnecessary, so remove that too.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---

I'll take this via the crc tree.

 arch/s390/lib/crc32-glue.c | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/arch/s390/lib/crc32-glue.c b/arch/s390/lib/crc32-glue.c
index 649ed7e8b99c..3c4b344417c1 100644
--- a/arch/s390/lib/crc32-glue.c
+++ b/arch/s390/lib/crc32-glue.c
@@ -59,21 +59,10 @@
 
 DEFINE_CRC32_VX(crc32_le_arch, crc32_le_vgfm_16, crc32_le_base)
 DEFINE_CRC32_VX(crc32_be_arch, crc32_be_vgfm_16, crc32_be_base)
 DEFINE_CRC32_VX(crc32c_arch, crc32c_le_vgfm_16, crc32c_base)
 
-static int __init crc32_s390_init(void)
-{
-	return 0;
-}
-arch_initcall(crc32_s390_init);
-
-static void __exit crc32_s390_exit(void)
-{
-}
-module_exit(crc32_s390_exit);
-
 u32 crc32_optimizations(void)
 {
 	if (cpu_has_vx()) {
 		return CRC32_LE_OPTIMIZATION |
 		       CRC32_BE_OPTIMIZATION |

base-commit: 34a3ebfb22d694cc07addae5ce0a8f83139592bd
-- 
2.49.0


             reply	other threads:[~2025-04-17 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 16:38 Eric Biggers [this message]
2025-04-21  7:51 ` [PATCH] s390/crc32: Remove no-op module init and exit functions Heiko Carstens

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=20250417163829.4599-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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