Messages in this thread | | | Date | Tue, 11 Apr 2017 13:12:28 +0800 | From | Herbert Xu <> | Subject | Re: linux-next: manual merge of the crypto tree with the kbuild tree |
| |
On Tue, Apr 11, 2017 at 03:02:50PM +1000, Stephen Rothwell wrote: > > So basically we need CRYPTO_MAX_ALG_NAME to be 64 in the exported > header but 128 in the kernel header? In which case the kbuild patch > needs to be changed not removed. Or the merge resolution needs to be > cleverer.
Actually the kbuild patch just needs to be reverted. We should not export CRYPTO_MAX_ALG_NAME at all. Each user-space interface that uses it already has its own limit and should not refer to the in-kernel value.
Cheers, -- Email: Herbert Xu <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
| |