Hi! I have pushed updates to lts-commit-lists, it should now include reviews up-to 5.10.55 and 4.19.200. I'm not primarily focusing on reviewing 4.4.X patches, but due to way reviews are done, I have

Hi! 4.4 is very different in that area, and KVM is not exactly our focus. A lot of research would be needed. I guess we can simply ignore this one. Yes, speculation is huge problem, and getting BPF ri

Hi! Thank you, it was very useful for getting 4.4-rt released. I noticed that linux-4.4.y-cip-rebase was not updated, but as there were no changes between -cip59 and -cip60, it did not pose a problem.

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.277-rt224 is out, and it would be useful to do -cip-rt release based on that. Would it be possible to do -cip release based on 4.4.277? Thank you, Pavel -- DENX Software Engineering GmbH, Mana

Hi! Thank you. Note that I pushed my comments into the repository, so you may want to do the pull before doing changes there. Best regards, Pavel

Hi! This is basically missing memset. Does not look evil to backport. This may need more careful look. There are 4 patches fixing this in mainline, but only two in 5.10. c7da1d1ed43a6c2bece0d287e2415a

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! This is sad situation but we don't need to do anything here. Too early to do anything here, we don't have enough information. Too early to do anything here, we don't have enough information. Stabl

Hi! I tried to release 4.4-cip-rt at the end of May, but suitable versions were not available, and I got nasty-looking rejects when trying to sort things out. We decided to (try to) coordinate -cip re

Hi! My notes are below. On IRC, I wrongly assumed that "CAN BCM" refers to some kind of driver. Unfortunately, it is generic code, and it is used by some of our configs. This is in early stages, it is

Hi! We have outstanding action item about these two, but at this point I believe we should simply start monitoring these: CVE-2021-3444 -- this is about BPF handling. It does not look like easy backpo

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! Thanks a lot for doing this (and sorry for all the false positives from the script). I went through the list for entries where existing commit was not identified, and this is the result: It looks

Hi! Thanks for doing this, let me take a look. Best regards, Pavel

Hi! I re-tried, and now I got this: https://lava.ciplatform.org/scheduler/job/302528 I'll retry once more, I believe it will go way. Best regards, Pavel

Hi! Looks good to me. I'll apply it if there are no other comments. Best regards, Pavel

Hi! This is one of the common failures: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/1364210937 The other one was not seen today. Uploading binaries 79------------------ 80uplo

Hi! In last import, CVE-2020-36385 and CVE-2020-36386 was confused. That's fixed now. And we have following new issues: * 2021-06-13 CVE-2021-0129 -- Passkey Entry protocol of the Bluetooth Core is vu

Hi! You are right, something went wrong with the import. It is corrected now. Best regards, Pavel