On 14 May 2013 18:49, Jon Medhurst (Tixy) <t...@linaro.org> wrote: > > This also enables CONFIG_CRYPTO_SHA1 which we didn't already have > enabled in our builds, so I assume nothing actually needs this option. > If that's true, then it doesn't seem worth enabling an optimised version > of code which isn't going to be used. ;-) >
Good point. However, if I use merge_config to generate eg. arndale/ubuntu, I end up with a .config which does have SHA1 and AES enabled. So what would be the best way to enable CONFIG_CRYPTO_SHA1_ARM automatically if some more specific config fragment enables CONFIG_CRYPTO_SHA1 (and CONFIG_ARM), even if only through implicit dependencies? -- Ard. _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
