From: Quirin Gylstorff <quirin.gylstorff@...> This Updates the ISAR revision cf3f18a649ff42726677a58b224b9bb58ea4ba46 and converts the swupdate recipes to the usage of

From: Quirin Gylstorff <quirin.gylstorff@...> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> --- recipes-core/swupdate/swupdate.inc | 12 ++----------

Thanks for sharing this Masami, I've been looking into pre-cgroup_ns backport too. The condition to allow modifying release_agent is two-fold: a) caller is capabable(CAP_SYS_ADMIN), b) cgroup_ns is

Hello Pavel, FYI the best place to check out results from CIP trees is https://kernelci.ciplatform.org/. (which redirects to CIP specific results from kernelci.org) KernelCI is currently monitoring

Hi! I pushed a test commit to ci/pavel/linux-test. This is not first commit in the 14 days. Where can I get the results? I don't see them at https://linux.kernelci.org/test/ . pavel@amd:~/cip/4$

Hi! I'm trying to understand how to work with kernelci. I thought I'd start with understanding 4.4.302 results, so I went to examine some. a) qemu failing I got

From: "Eric W. Biederman" <ebiederm@...> commit 24f6008564183aa120d07c03d9289519c2fe02af upstream. The cgroup release_agent is called with call_usermodehelper. The

How about ia32 and aarch64 (even if the debian package does not support them yet)? Why making this configurable? Why making this a list? Do you see use cases beyond current EBG releases and recipes

From: Quirin Gylstorff <quirin.gylstorff@...> This preparing isar-cip-core to integrate the upcomming ISAR features sstate and sbuild. Sbuild doesn't allow the extraction of build

Most of them - we still have the Embedded lua handler which will stay as it make no sense for upstream. And as long as we support Buster - these patches will also stay. Quirin

From: Jan Kiszka <jan.kiszka@...> We have a release - and a recipe for it since a37064660730. Signed-off-by: Jan Kiszka <jan.kiszka@...> --- conf/distro/cip-core-bullseye.conf | 4

Thanks, applied. I suspect you already sent the embedded patch to Debian as well, right? Jan -- Siemens AG, Technology Competence Center Embedded Linux

DEPLOY_DIR is no longer used now. Also, why do we need a parameter here? It's about the Isar way of installing the Isar-built EBG binary. All we need is to probe the target architecture. IIRC, we

cip/linux-4.4.y-cip-rt baseline: 72 runs, 6 regressions (v4.4.302-cip68-rt38) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig |

cip/linux-4.4.y-cip-rt build: 169 builds: 5 failed, 164 passed, 6 errors, 35 warnings (v4.4.302-cip68-rt38) Full Build Summary:

cip/linux-4.4.y-cip baseline: 85 runs, 12 regressions (v4.4.302-cip68) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig |

cip/linux-4.19.y-cip baseline: 101 runs, 16 regressions (v4.19.229-cip67) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip/linux-4.4.y-cip build: 182 builds: 5 failed, 177 passed, 6 errors, 37 warnings (v4.4.302-cip68) Full Build Summary:

cip/linux-4.19.y-cip build: 105 builds: 0 failed, 105 passed, 18 warnings (v4.19.229-cip67) Full Build Summary: https://kernelci.org/build/cip/branch/linux-4.19.y-cip/kernel/v4.19.229-cip67/ Tree:

My understanding is that we are maintaining both 4.4-cip and 4.4-cip-rt going forward. I hope it is achievable. Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: