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

Ben Hutchings pushed to branch masterat cip-project / cip-kernel / cip-kernel-secCommits: 3ed9dc6d by Daniel Sangorrinat 2019-06-17T20:14:31Zremotes: refer to configuration filesThe Readme indicated

I've applied this and the following patch, as they're obviously correct. Ben. -- Ben Hutchings, Software Developer   Codethink Ltd https://www.codethink.co.uk/

On Thu, 2019-06-20 at 14:51 +0900, Daniel Sangorrin wrote: [...] > --- a/scripts/kernel_sec/branch.py > +++ b/scripts/kernel_sec/branch.py [...] > +def check_git_repo(git_repo, remotes,

I've been promising for some time to provide a way to identify which changes on Linux stable branches are relevant to CIP members, and conversely which are irrelevant and don't need to be

From: Mika Westerberg <mika.westerberg@...> commit 089bd46d8bc1fe5a28351e82e4adcaa5a40121b5 upstream. Kbuild test robot reports: drivers/spi/spi-pxa2xx.c: In function ‘setup_cs’:

Hi all, CIP kernel team has released Linux kernel 4.19.52-cip4 and 4.4.182-cip34 for SACK Panic[0]. You can get this release via the git tree at: 4.19.52-cip4: repository:

Hi!

Allow reporting on cip branches, instead of returning an error like this one: $ ./scripts/report_affected.py linux-4.4.y-cip Traceback (most recent call last): File "./scripts/report_affected.py",

Hello Ben,