Hi! New realtime trees should be available at kernel.org. Trees are available at https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt https://git.kernel.org/pub/

Hi! 4.4.285-rt226 is out it would be good to make it into -cip-rt release. Would it be possible to create 4.4.285-cip release to make it easier? Thanks and best regards, Pavel ----- Forwarded message

Hi! On cip-members, there was question of widely used drivers that we should include for WIFI or Bluetooth. AFAICT there are no standartized interfaces for WIFI, and each vendor has their own. For Blu

Hi! On cip-members there's discussion about quality of selected wireless drivers. AFAICT we are reviewing changes to those drivers on -stable series (good). We are not testing the drivers in any meani

Hi! I guess I should mention alternate possibilities. We could try to somehow "hash" the commits... Perhaps I'd review all the patches where upstream sha begins with 0-6. But patches in -stable often

Hi! It is good to review "stable" patches soon, because such reviews are more useful for the stable community, and because when bug is spotted, it is easier to get patch dropped in the 5.10.X-rc phase

Hi! It is not first time I see this failure: https://lava.ciplatform.org/scheduler/job/444336 [[0;32m OK [0m] Started Login Service. [[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host

Hi! I'm travelling tommorow and day after that, so I may not make it to the irc meeting. I have reviewed patches for 5.10.64, 65 and 66. Best regards, Pavel -- DENX Software Engineering GmbH, Managing

Hi! New realtime trees should be available at kernel.org. Trees are available at https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt https://git.kernel.org/pub

Hi! I don't think we need to care about this one. Embedded systems don't usually run untrusted code... This is already queued to 4.4 and 4.19; we can simply wait. KVM. Tricky code and not exactly focu

Hi! These summaries are not so short; I simply skip them and go to full list. Perhaps they don't need to be included, or could include only CVEs where we need to take an action? This one is queued for

Hi! Hmm, no; that is what original code did and what is known not to work for reasons I don't fully understand. Anyway, I asked on the lists, and according to Thadeu Lima de Souza Cascardo Ubuntu did

Hi! At least some of the relevant fixes are queued for 5.10.61/4.19. Likely this will resolve itself. I took a look into this. Apparently 4.14 and 4.19 is affected. ( https://seclists.org/oss-sec/2021

Hi! I was going through CVE entries for a month or so and these accumulated in that time. Would it make sense to add them to the current "watch list"? ** Bluetooth Unfortunately, not enough info is pr

Hi! I tried to look at this, and it is rather non-trivial. In particular, I'd not know how to test it. I ended up with this patch, but it is not even compile-tested. Best regards, Pavel diff --git a/D

Hi! I was at TSC Zoom meeting but did not realize consequences. I have scheduling conflict this week, so I'll most likely not make it. Best regards, Pavel

Hi! Thank you, it seems to be better now, and it looks like ctj_zynqmp is available, too (I have not yet seen successful test, but it at least tries). But I still see problems with x86_qemu... the "2h

Hi! > > > * CVE detail > > > > > > New CVEs > > > > > CVE-2021-38205: net: xilinx_emaclite: Do not print real IOMEM pointer > > > > > > xemaclite_of_probe() in drivers/net/ethernet/xilinx/xilinx_emacl

Hi! This affects our kernels (I looked at 5.10.57 and 4.4.277). On one hand we could ask for backport, on the other... I'm not sure it is serious enough to warrant any action. Best regards, Pavel

Hi! -stable-rc testing seems to be failing more than usual. This is the "usual" failure: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/1493077012 WARNING: Retrying... error=inva