Hi! So this needs more investigation and possibly 4.4 port? 08b64fc looks quite small/simple. ...and 4.19 and older is fixed, and 5.10 already contains f8d4f44df056c5b504b0d49683fb7279218fd207, so

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Our channel is the following: irc:irc.libera.chat:6667/cip The IRC meeting

Hi ! It's this week's CVE report. This week reported 7 new CVEs. * New CVEs CVE-2021-39633: ip_gre: add validation for csum_start CVSS v3 score is not provided An information leak bug was found

cip/linux-5.10.y-cip sleep: 8 runs, 2 regressions (v5.10.83-cip1-150-ge27e063993d9) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip/linux-5.10.y-cip ltp-ipc: 8 runs, 1 regressions (v5.10.83-cip1-150-ge27e063993d9) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip/linux-5.10.y-cip baseline: 169 runs, 1 regressions (v5.10.83-cip1-150-ge27e063993d9) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig |

cip/linux-5.10.y-cip build: 190 builds: 3 failed, 187 passed, 4 errors, 10 warnings (v5.10.83-cip1-150-ge27e063993d9) Full Build Summary:

Hi! Thank you, applied. Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

cip/linux-5.10.y-cip sleep: 8 runs, 1 regressions (v5.10.83-cip1-89-ga7f9ee34265b) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig

cip/linux-5.10.y-cip baseline-nfs: 23 runs, 1 regressions (v5.10.83-cip1-89-ga7f9ee34265b) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig |

cip/linux-5.10.y-cip build: 190 builds: 3 failed, 187 passed, 4 errors, 10 warnings (v5.10.83-cip1-89-ga7f9ee34265b) Full Build Summary:

Hi! Thank you. The patches look good to me. You may want to include sha1 hash on the first line of changelog as [ Upstream commit c1833c3964d5bd8c163bd4e01736a38bc473cb8a ] ...as that's what's

I will submit the patches to stable. Thanks. Amy

Hi! Ok, this is really taking nice small steps. Thanks :-). You could help reviewers a bit more by saying "no functional changes" when there are none, but this was already very good job. I could not

Hi! Ok, good. Patches passed testing (zynqmp board has problems but they are not kernel related) and I have pushed them. Best regards, Pavel -- DENX Software Engineering GmbH, Managing

Hi! Thank you for answers. Is there reason not to submit it to stable? You are describing it is as a bugfix, and Greg takes those. [Advantages are a) community review, b) less patches to maintain for

We haven't been able to reproduce the issue but apparently it's being reproduced periodically. The offending patch doesn't appear in linux-4.4.y-cip linux-5.10.y-cip has the fix already. Both

Hi Pavel, Thanks for the feedback. I thought it is simple. Since we haven't made any release, history modification and force pushing is not required, as this patch will be part of upcoming

Patch application in unfortunate order is a very common issue in upstream: dependencies are missed, patches take different routes through different maintainer trees, bugs get fixed only after the

Hi! Series looks okay to me. I did not test it but I assume it will pass. I can test/apply it quickly if history modification and force push is not required. I'd like confirmation from rest of the