Hello Robert, You are correct. I am (as I email to the list about V2) finding more info about the Lava framework. The fact is that, since Lava 2017.2 Version 2 is first usable version along with

Hello CIP members, As I look at the git repository, there are multiple PREEMPT_RT branches: * linux-4.4.y-cip-rt-rebase * linux-4.4.y-cip-rt * linux-4.4.y-cip-rt-patches I'm trying to understand

Zoran "zoran.stojsavljevic.de" <zoran.stojsavljevic.de@...> writes: We've been using LAVA v 2 from the start (well at least from the 0.9 release and maybe earlier). We're still using LAVA

Hello Robert, As I am continuing to investigate this issue with the testing framework, apparently Linaro does NOT support anymore Lava V1 (decisively), they already switched to Lava V2 (please, see

All looks good to me.  I've applied and pushed these changes. Ben. -- Ben Hutchings Software Developer, Codethink Ltd.

All looks good to me. I've applied and pushed these changes. Ben. -- Ben Hutchings Software Developer, Codethink Ltd.

Hi, in order to increase the visibility of the work done in Gitlab I suggest one of these two actions: * Create a mailing list for development notifications where we can send the notifications of

Hi Daniel, Argh :) This should read patch-4.4.112-cip18-rt11.patch.xz Yes. these are the right URLs. Right, I'll stop doing the patches. Good to hear that the cip-rt works for

Hi Daniel, Thanks for letting me know. The correct URL is https://www.kernel.org/pub/linux/kernel/people/wagi/cip-rt/4.4/ I just create the patches on top of the CIP version. The scripts for this

Dear members of the CIP TSC, My name is Jeff ErnstFriedman and I will be stepping in with program management for CIP. I am pleased to meet everyone and would like to make myself available for any

Greetings all, Unfortunately, I have a conflict for the TSC and Marketing Meetings on Monday, so will not be able to attend. Cheers, Annie Annie Fisher, MPA CSM Program Manager, The Linux

Signed-off-by: Biju Das <biju.das@...> Signed-off-by: Chris Paterson <chris.paterson2@...> Signed-off-by: Simon Horman <horms+renesas@...> (cherry picked from commit

Document i2c Device Tree support for RZ/G1[ME] (also known as r8a774[35]) SoCs. They are compatible with R-Car Gen2 SoC family. No driver change is required as the initialisation sequence is currently

From: Simon Horman <horms+renesas@...> Add per-Generation fallback bindings for R-Car SoCs. This is in keeping with the compatibility string scheme is being adopted for drivers for Renesas

Add the I2C[0-5] devices to the r8a7743 device tree. Signed-off-by: Biju Das <biju.das@...> Signed-off-by: Simon Horman <horms+renesas@...> (cherry picked from commit

Document i2c Device Tree support for RZ/G1[ME] (also known as r8aA774[35]) SoCs. They are compatible with R-Car Gen2 SoC family. Signed-off-by: Biju Das <biju.das@...> Acked-by: Simon

From: Simon Horman <horms+renesas@...> In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 2 and Gen 3. But beyond that it's not clear what