From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Cc: Johannes Zink <j.zink@pengutronix.de>
Subject: [PATCH 4/4] crypto: crc32: enable for PBL
Date: Mon, 4 Sep 2023 10:18:25 +0200 [thread overview]
Message-ID: <20230904081825.1997618-4-s.hauer@pengutronix.de> (raw)
In-Reply-To: <20230904081825.1997618-1-s.hauer@pengutronix.de>
A crc32 implementation might be useful for PBL as well, so enable it.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
crypto/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/crypto/Makefile b/crypto/Makefile
index 22035d4f69..4a1c7e9615 100644
--- a/crypto/Makefile
+++ b/crypto/Makefile
@@ -1,6 +1,6 @@
# SPDX-License-Identifier: GPL-2.0-only
-obj-$(CONFIG_CRC32) += crc32.o
+obj-pbl-$(CONFIG_CRC32) += crc32.o
obj-pbl-$(CONFIG_CRC_ITU_T) += crc-itu-t.o
obj-$(CONFIG_CRC7) += crc7.o
obj-$(CONFIG_DIGEST) += digest.o
--
2.39.2
next prev parent reply other threads:[~2023-09-04 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 8:18 [PATCH 1/4] crypto: crc32: Drop CONFIG_DYNAMIC_CRC_TABLE option Sascha Hauer
2023-09-04 8:18 ` [PATCH 2/4] crypto: crc32: Lindent Sascha Hauer
2023-09-04 8:18 ` [PATCH 3/4] crypto: crc32: allocate crc_table statically Sascha Hauer
2023-09-04 8:18 ` Sascha Hauer [this message]
2023-09-07 5:48 ` [PATCH 1/4] crypto: crc32: Drop CONFIG_DYNAMIC_CRC_TABLE option Johannes Zink
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=20230904081825.1997618-4-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=j.zink@pengutronix.de \
/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