[Question] Why disable CRYPTO_SM4/CRYPTO_SM3?

To: "debian-kernel@lists.debian.org" <debian-kernel@lists.debian.org>
Cc: 张宁 <zhangn1985@outlook.com>
Subject: [Question] Why disable CRYPTO_SM4/CRYPTO_SM3?
From: 张宁 <zhangn1985@outlook.com>
Date: Mon, 14 Dec 2020 05:26:33 +0000
Message-id: <[🔎] TYBP286MB0221577C24CA58E5E30F35B9CDC70@TYBP286MB0221.JPNP286.PROD.OUTLOOK.COM>

Hi, Bastian Blank

I find in master branch, CRYPTO_SM4/CRYPTO_SM3 are disabled without clean justification.

could you tell us why?

https://salsa.debian.org/kernel-team/linux/-/commit/3825c0accbd374d8ed4c9f8a9a516093e41cbe43
https://salsa.debian.org/kernel-team/linux/-/commit/2ea9b54f869dfdcb4ebc2cf0de2e60d3c83ac988

BR.
Ning.

Reply to:

Follow-Ups:
- Re: [Question] Why disable CRYPTO_SM4/CRYPTO_SM3?
  - From: Bastian Blank <waldi@debian.org>

Prev by Date: Bug#975686: In kernel 5.10 rc7
Next by Date: Processed: reassign 977262 to nvidia-legacy-340xx-driver, forcibly merging 976056 977262
Previous by thread: Bug#975686: In kernel 5.10 rc7
Next by thread: Re: [Question] Why disable CRYPTO_SM4/CRYPTO_SM3?
Index(es):
- Date
- Thread