From: Chuck Lever <chuck.lever@xxxxxxxxxx>
On Sun, 03 Aug 2025 14:21:30 -0700, Eric Biggers wrote:
> Now that nfsd is accessing SHA-256 via the library API instead of via
> crypto_shash, there is a direct symbol dependency on the SHA-256 code
> and there is no benefit to be gained from forcing it to be built-in.
> Therefore, select CRYPTO_LIB_SHA256 from NFSD (conditional on NFSD_V4)
> instead of from NFSD_V4, so that it can be 'm' if NFSD is 'm'.
>
>
> [...]
Applied to nfsd-testing, thanks!
[1/1] nfsd: Don't force CRYPTO_LIB_SHA256 to be built-in
commit: 9c0d70a41f389ff1f15fd38fa47be5c3dd13c915
--
Chuck Lever
