<daniel.sangorrin@...> wrote: I believe it would be better to include the "CVE => " string in the full text passed to textwrap. That would make all lines properly wrapped at the

Hi Kudo-san, Sorry, I can not participate IRC meeting today.

Hi,

Hi Pavel,

Hi Kudo-san and all, I'll be absent today. And, I'll report here as an alternative to attendance. Both minor updates were once reported, but since they are protracted, I will summarize again

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. *Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting

Hi! Yes, and the revert is now queued to 4.19-stable, too. So.. what do we want to do here? We can merge 4.19.151 to -cip when it is released, and I can then release new -cip-rt that works on

Hello Ben, Thanks a lot for your review and sorry for taking your time. We will have an internal review and take your comments into account to prepare a new proposal. Kind regards, Daniel

Hi, FYI: https://patchwork.ozlabs.org/project/netdev/patch/20200922072931.2148-1-geert+renesas@.../ Best regards, Nobuhiro

[...] I think this script is trying to do too many different things: 1. Importing data from NVD 2. Importing data from Debian security tracker 3. Parsing an existing report (!) 4. Generating a new

Hi, This issue seems to occur randomly. # cip+rt kernel NG: https://lava.ciplatform.org/scheduler/job/57129 https://lava.ciplatform.org/scheduler/job/57842 OK:

Hi! Yes, I did that, as the changelog explains. Sorry. I had to select from few bad options: 4.19.147-rt release is not available and previous release is too old. So -cip-rt is based on 4.19.148-rt,

Hello Pavel, Thank you for the release. So we're releasing a Kernel that we know doesn't boot on one of CIP's reference platforms? Or did you already revert the above patch as part of your

This is just a copy-out, I don't see the chroot need here. Please avoid code duplication. We have means like "require some.inc" in bitbake. I'm also wondering if this should go to isar upstream

Hi! New realtime trees should be available at kernel.org. Trees are available

Hi! And this one seems to be responsible. I believe -cip will need to do something with it when it tries to merge 4.19.148... I hit it early because 4.19.147-rt is not available, so I merged

Hi! I re-ran the test with same sources, and failure is still there. I tried rt+v4.19.147-cip35 -- e8bcfc1349886ef3cf6625a0bc9cd25ddf80112c -- fails, too. Let me try commit

Hi! I got test failure when I submitted -rt branch for testing. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/197703780 This seems to be "real" failure: [ 2.791351]

Hi! v4.4.235-cip49-rt31 should be available at kernel.org. Trees are available

Hi all,