cip-gitlab/ci/pavel/linux-test kselftest-futex: 5 runs, 4 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regress

cip/linux-4.4.y-cip smc: 4 runs, 1 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions ------------+-----

cip/linux-4.4.y-cip ltp-pty: 3 runs, 1 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions --------------

cip/linux-4.4.y-cip ltp-ipc: 7 runs, 1 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions --------------

cip/linux-4.4.y-cip ltp-fcntl-locktests: 3 runs, 1 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions --

cip-gitlab/ci/pavel/linux-test baseline: 44 runs, 17 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions

cip-gitlab/ci/pavel/linux-test baseline-nfs: 21 runs, 14 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressi

cip/linux-4.4.y-cip baseline: 45 runs, 1 regressions (v4.4.302-cip70-236-g69445bc0d4209) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions ------------

Hi! I have merged 4.4-st trees to 4.4-cip, so there should be good time to do 4.4-cip release. (Tests are still running, but there's good chance they'll be ready when you'll read this). Best regards,

cip-gitlab/ci/pavel/linux-test build: 185 builds: 5 failed, 180 passed, 6 errors, 41 warnings (v4.4.302-cip70-236-g69445bc0d4209) Full Build Summary: https://kernelci.org/build/cip-gitlab/branch/ci%2F

cip/linux-4.4.y-cip build: 180 builds: 0 failed, 180 passed, 41 warnings (v4.4.302-cip70-236-g69445bc0d4209) Full Build Summary: https://kernelci.org/build/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-c

Hi! Results were pushed to -st-rc. I have added "KNOWN-BUGS" with ... well.. some documentation, and commit f077ac447faf72436e0a7e153695bbf1fccbcd68 is worth checking. Unfortunately, that tcp stuff is

From: Sven Schultschik <sven.schultschik@...> The secure boot setup with OP-TEE, u-boot and EFI works with a platform key (pk), key exchange key (kek) and signature database (db). isar-cip-core should

From: Sven Schultschik <sven.schultschik@...> The snakeoil keys are copied to the deploy folder if machine is qemu-arm64. The RPMB qemu workaround is not persistent and for that the keys need to be pr

From: Sven Schultschik <sven.schultschik@...> The start-qemu shell script need some adjustments to switch on secure in the machine statement and adds the virtual random number generator if secure boot

From: Sven Schultschik <sven.schultschik@...> provide a recipe to generate the needed binary to start a secure boot qemu with integrated optee and active RPMB replay protected memory emulation within

From: Sven Schultschik <sven.schultschik@...> Qemu itself is missing a implemented emulation of an RPBM (replay protected memory) which is part of an emmc. Therefore currently a u-boot patch, which ad

From: Sven Schultschik <sven.schultschik@...> Optee is part of u-boot In the secureboot scenario to use optee and RPMB as secure storage. Signed-off-by: Sven Schultschik <sven.schultschik@...> --- rec

From: Sven Schultschik <sven.schultschik@...> The recipe provides the possibility to create optee-os binaries for use inside of an qemu secureboot setup with edk2, rpmb, u-boot and uefi Signed-off-by:

From: Sven Schultschik <sven.schultschik@...> This series of patches will add recipes to build a QEMU setup which uses OP-TEE to use RPMB (Replay protected memory) of an EMMC for a secure storage. Whi