On Mon, Aug 12, 2019 at 10:40:49PM +0300, Jussi Kivilinna wrote: > That's quite complicated approach. Fast and easier process would be if you > just own the patch yourself. Libgcrypt (and target file in libgcrypt) > is LGPL v2.1+, so the license is compatible with kernel and you are good > to go with just your own (kernel DCO) signed-off-by. > > -Jussi
I have gone this route as another developer pointed out that we can eliminate all of the inline asm umul_ppmm definitions because the kernel requires GCC 4.6 and newer and that is completely different from the libgcrypt patches. https://lore.kernel.org/lkml/[email protected]/ Thanks for weighing in and cheers! Nathan
