On 2019/4/15 上午11:42, kai.k...@windriver.com wrote:
From: Kai Kang <kai.k...@windriver.com>

Update SRCREV of cryptodev which only contains one fix for linux 5.0:

$ git log 
fd8b15ef1c8398a69a37932ee48c74ab40329a29..f971e0cd4a0ebe59fb2e8e17240399bf6901b09b
commit f971e0cd4a0ebe59fb2e8e17240399bf6901b09b
Author: Derald D. Woods <woods.techni...@gmail.com>
Date:   Sun Feb 10 13:22:19 2019 -0600

     Fix module loading with Linux v5.0-rc5

     This commit fixes this module load error:
     [...]
     [   29.112091] cryptodev: loading out-of-tree module taints kernel.
     [   29.128906] cryptodev: Unknown symbol crypto_givcipher_type (err -2)
     [   29.188842] cryptodev: Unknown symbol crypto_givcipher_type (err -2)
     modprobe: can't load module cryptodev (extra/cryptodev.ko): unknown symbol 
in module, or unknown parameter
     [...]


Without this patch it fails to modprobe module cryptodev. Ping.

Kai



     Upstream Linux support for unused GIVCIPHER, and others, was dropped here:

     c79b411eaa72 (crypto: skcipher - remove remnants of internal IV generators)

     Signed-off-by: Derald D. Woods <woods.techni...@gmail.com>

Signed-off-by: Kai Kang <kai.k...@windriver.com>
---
  meta/recipes-kernel/cryptodev/cryptodev.inc | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/cryptodev/cryptodev.inc 
b/meta/recipes-kernel/cryptodev/cryptodev.inc
index 252d39d23a..79ddefd435 100644
--- a/meta/recipes-kernel/cryptodev/cryptodev.inc
+++ b/meta/recipes-kernel/cryptodev/cryptodev.inc
@@ -4,7 +4,7 @@ LICENSE = "GPLv2"
  LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
SRC_URI = "git://github.com/cryptodev-linux/cryptodev-linux"
-SRCREV = "fd8b15ef1c8398a69a37932ee48c74ab40329a29"
+SRCREV = "f971e0cd4a0ebe59fb2e8e17240399bf6901b09b"
S = "${WORKDIR}/git"


--
Kai Kang

--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to