Hello Quirin, Thank you for the patch. Should be r8a774a1-hihope-rzg2m-ex.dtb. The 'ex' is the sub-board that adds Ethernet/PCIe/CAN etc. Just to check, where did you copy this config from? Is there a

Hello all, Just a heads up that the Renesas LAVA lab (lab-cip-renesas) will be offline for 2/3 hours on the morning of the 13th November, from around 1000 GMT onwards. Our hardware is being PAT tested

Thank you Ben. Looping in the mailing list for general interest. Kind regards, Chris

Hello Pavel, Just to let you know, the arm64 boards are currently offline in the Renesas LAVA lab. I'm working to get them online again, but the impact will be that your test jobs will eventually time

Hello all, For your testing pleasure I've added two more RZ/G1M platforms (r8a7743-iwg20d-q7) to the Renesas LAVA worker, bringing the total to 4. Hopefully will speed up testing a bit. A complete lis

Hello Pavel, all, Yep. Yes, this is an issue. Although I guess it's a fairly easy merge, albeit an annoying one. Agreed, it's not ideal. We can, and I already have a bit with the LTS stable rc testing

Ah, sorry. Too late! Feel free to disregard the -rt patches. Kind regards, Chris

Setting a relevant test timeout is hard as we've no idea how many other test jobs are running. We have another two timeouts already: 1) The CI job timeut setting in the GitLab runner 2) The LAVA test

We should concentrate our testing on the offical configurations. We're essentially testing shmobile_defconfig anyway. Signed-off-by: Chris Paterson <chris.paterson2@...> --- v1 -> v2 * No chan

This will allow tests to run as soon as the corresponding build job is complete. This will help spread the load on the test infrastructure and save time. Signed-off-by: Chris Paterson <chris.paterson2

Setting a relevant test timeout is hard as we've no idea how many other test jobs are running. We have another two timeouts already: 1) The CI job timeut setting in the GitLab runner 2) The LAVA test

We should concentrate our testing on the offical configurations. We're essentially testing shmobile_defconfig anyway. Signed-off-by: Chris Paterson <chris.paterson2@...> --- v1 -> v2 * No chan

This will allow tests to run as soon as the corresponding build job is complete. This will help spread the load on the test infrastructure and save time. Signed-off-by: Chris Paterson <chris.paterson2

Missing: needs: ["build:arm_renesas_shmobile_defconfig"] Missing: needs: ["build:arm_shmobile_defconfig"] I'll send a v2 for the series. Kind regards, Chris

Missing: needs: ["build:arm_renesas_shmobile_defconfig"] Missing: needs: ["build:arm_shmobile_defconfig"] I'll send a v2 for the series. Chris

Setting a relevant test timeout is hard as we've no idea how many other test jobs are running. We have another two timeouts already: 1) The CI job timeut setting in the GitLab runner 2) The LAVA test

We should concentrate our testing on the offical configurations. We're essentially testing shmobile_defconfig anyway. Signed-off-by: Chris Paterson <chris.paterson2@...> --- .gitlab-ci.yml | 3

This will allow tests to run as soon as the corresponding build job is complete. This will help spread the load on the test infrastructure and save time. Signed-off-by: Chris Paterson <chris.paterson2

Setting a relevant test timeout is hard as we've no idea how many other test jobs are running. We have another two timeouts already: 1) The CI job timeut setting in the GitLab runner 2) The LAVA test

We should concentrate our testing on the offical configurations. We're essentially testing shmobile_defconfig anyway. Signed-off-by: Chris Paterson <chris.paterson2@...> --- .gitlab-ci.yml | 3