On Wed, Oct 26, 2016 at 10:48 AM, Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote: > On 10/25/16 19:51, Stephen Rothwell wrote: >> Hi all, >> >> There will probably be no linux-next releases next week while I attend >> the Kernel Summit. >> >> Changes since 20161025: >> > > on x864_64: > > ERROR: "crypto_acomp_scomp_alloc_ctx" [crypto/acompress.ko] undefined! > ERROR: "crypto_acomp_scomp_free_ctx" [crypto/acompress.ko] undefined! > ERROR: "crypto_init_scomp_ops_async" [crypto/acompress.ko] undefined! > > > Full randconfig file is attached. crypto/acompress.o ----> crypto/Makefile:obj-$(CONFIG_CRYPTO_ACOMP2) += acompress.o crypto/Kconfig:config CRYPTO_ACOMP2 crypto/Kconfig: tristate paul@builder:~/git/linux-head$ git grep crypto_acomp_scomp_alloc_ctx crypto/acompress.c: return crypto_acomp_scomp_alloc_ctx(req); crypto/scompress.c:struct acomp_req *crypto_acomp_scomp_alloc_ctx(struct acomp_req *req) include/crypto/internal/scompress.h:struct acomp_req *crypto_acomp_scomp_alloc_ctx(struct acomp_req *req); paul@builder:~/git/linux-head$ So, no EXPORT_SYMBOL, and any .config which has ACOMP2=m will fail. Paul. -- > > -- > ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
