On 10-3-2017 10:52, Johannes Berg wrote: > On Fri, 2017-03-10 at 10:49 +0100, Arend Van Spriel wrote: >> >> On 10-3-2017 7:34, Johannes Berg wrote: >>> On Thu, 2017-03-09 at 12:57 +0000, Arend van Spriel wrote: >>>> Since v4.11-rc1 the patch file for crypto/ccm.c, which is >>>> incorporated >>>> in the compat module, no longer applies. Update the patch file to >>>> fix >>>> the issue. >>> >>> I think I want to get rid of this ccm thing entirely, any >>> objections? >>> As I remember, it doesn't actually work properly anyway. >> >> No objection here. Does the same apply to skcipher stuff? > > I think so, but not sure. > >>> I suspect that if we really can't do anything else, we'd have to >>> provide a backport for all of crypto/, but I don't want to go there >>> and >>> would rather mandate that all the crypto things are enabled in the >>> base >>> kernel. >> >> But that can only work when crypto api in base kernel and backport >> kernel are the same, right? > > No, I meant adding all of crypto/ to copy-list and making sure *that* > works across kernels ... Understand. There seem to have been significant changes in crypto land making this a challenge. Still seems like right idea. Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe backports" in
