Am Freitag, 5. Oktober 2018, 15:46:29 CEST schrieb Jason A. Donenfeld:

On Fri, Oct 5, 2018 at 3:38 PM Richard Weinberger
[off-list ref] wrote:

quoted

So we will have two competing crypo stacks in the kernel?
Having a lightweight crypto API is a good thing but I really don't like the idea
of having zinc parallel to the existing crypto stack.

No, as you've seen in this patchset, the dynamic dispatch crypto API
can trivially be done on top of Zinc. So each time we introduce a new
primitive to Zinc that's also in the dynamic dispatch API, we
reimplement the current crypto API in terms of Zinc. Check out the two
patches in this series that do this; it's quite clean and sleek.

This is why I was asking. Your statement and the code didn't match for me.
 

quoted

And I strongly vote that Herbert Xu shall remain the maintainer of the whole
crypto system (including zinc!) in the kernel.

No, sorry, we intend to maintain the code we've written. But I am
amenable to taking a tree-route into upstream based on whatever makes
most sense with merge conflicts and such.

 
So, you will be a sub-maintainer below Herbert's crypto, that's fine.
What you wrote sounded like a parallel world...

Thanks,
//richard