On Tue, Sep 11, 2018 at 04:02:52PM -0600, Jason A. Donenfeld wrote: > On Tue, Sep 11, 2018 at 3:47 PM Eric Biggers <ebiggers@xxxxxxxxxx> wrote: > > Of course, the real problem is that even after multiple revisions of this > > patchset, there's still no actual conversions of the existing crypto API > > algorithms over to use the new implementations. "Zinc" is still completely > > separate from the existing crypto API. > > No this is not, "the real problem [...] after multiple revisions" > because I've offered to do this and stated pretty clearly my intent to > do so. But, as I've mentioned before, I'd really prefer to land this > series through net-next Hi Jason Just as an FYI: 1) I don't think anybody in netdev has taken a serious look at the network code yet. There is little point until the controversial part of the code, Zinc, has been sorted out. 2) I personally would be surprised if DaveM took this code without having an Acked-by from the crypto subsystem people. In the same way, i doubt the crypto people would take an Ethernet driver without having DaveM's Acked-by. Andrew