Hi Pavel, I appreciate your effort. How about adding these questions into our question list and ask Wagner afterward :-) SZ

These were distracting when checking new code. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> --- scripts/import_stable.py | 8 +++++--- scripts/kernel_sec/branch.py | 4 ++--

Reporting on tags is useful for product engineers that have shipped a kernel with a specific tag and need to know which issues affect their product after some time. Signed-off-by: Daniel Sangorrin

This makes sure that we return when the user supplied branch names are not within the configured branches. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> ---

The previous code could not handle branches with names other than stable branch names. For example, passing "linux-4.4.y-cip" as a branch would return an error. Signed-off-by: Daniel Sangorrin

Helper script that prepares the local git repository with the configured remote branches. Expert developers and kernel maintainers will probably have their own worktrees but for new users or a

Add checks to make sure that the local repository exists and has the configured remotes in place. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> --- scripts/import_stable.py |

Hello Ben, This series contains a few fixes and support for reporting on tags. - Re-sent patches [cip-kernel-sec 1/6] check_git_repo: add checks to the local I decided to remove the repository

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: fd56a750 by Ben Hutchingsat 2019-06-24T15:40:59ZIgnore CVE-2019-0157 as it relates to an out-of-tree

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: dc96f854 by Ben Hutchingsat 2019-06-24T14:58:04ZImport more data11 changed

Hi! Well, most systems do not really need to protect local user's secrets from each other. We simply don't allow code execution for untrusted parties. If someone decides to combine "top secret

Hello, The lab is now back online. Kind Regards, Patryk

Hello all, I am bringing lab-cip-renesas offline to do some necessary LAVA maintenance. You will still be able to submit test jobs, but they won’t run until the lab is back online. The lab

Thanks for picking this up. Just like the regular -cip kernel, the -rt version's primary stable feed is merge-based. Rebasing only comes out of the fact that a second patch series is involved, but I

Hi! I played a bit with -rt kernels, and here are the results. v4.19.50-rt22-cip3-rebase was reasonably easy to do, as -cip1 was empty. v4.4.179-rt181-cip34-rebase was more interesting. Trees are

Hi! I believe they should go to the repository, because we may want to manually adjust the lists. I don't believe "example" configurations we have necessarily have enabled all the options "final

Hi Jan OK, great. Let me know when you update it, I want to update the SWUpdate branch as well. Thanks, Daniel

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: 4975a489 by Ben Hutchingsat 2019-06-20T20:26:18ZImport more data19 changed

In fact it would probably make more sense to get rid of this function altogether and put that code in reported_affected.py, which can avoid calling get_live_branches() multiple times. Ben. -- Ben

[...] [...] Does this function actually need to know anything about specific branch names? It seems like we should be able to implement it as something like: for branch