On 16/08/2019 10:18, Ard Biesheuvel wrote: > On Fri, 16 Aug 2019 at 10:29, Milan Broz <gmazyland@xxxxxxxxx> wrote: >> >> Hi Ard, >> >> On 15/08/2019 21:28, Ard Biesheuvel wrote: >>> Changes since v10: >>> - Drop patches against fscrypt and dm-crypt - these will be routed via the >>> respective maintainer trees during the next cycle >> >> I tested the previous dm-crypt patches (I also try to keep them in my kernel.org tree), >> it works and looks fine to me (and I like the final cleanup :) >> >> Once all maintainers are happy with the current state, I think it should go to >> the next release (5.4; IMO both ESSIV API and dm-crypt changes). >> Maybe you could keep sending dm-crypt patches in the end of the series (to help testing it)? >> > > OK. But we'll need to coordinate a bit so that the first patch (the > one that introduces the template) is available in both branches, > otherwise ESSIV will be broken in the dm branch until it hits another > branch (-next or mainline) that also contains cryptodev. Yes, I know. I'll ask Mike what is his preference here... For now, it should appear at least in the cryptodev tree :) ... > Any idea about the status of the EBOIV patch? It is in the queue for 5.4 (should be in linux-next already), I guess 5.4 target is ok here. https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-5.4 Milan
