On 2017-11-16 16:32, Ralf Ramsauer wrote:
> Hi Jan,
> 
> your patches are not yet merged to master, so I would suggest to squash
> them to a non bug-introducing series. Just to avoid adding ~600 lines
> and to remove them in the next step.

In fact, I've already dropped the build-breaking commits at least. I can
take patch 1 on top, though, because no existing user was affected by it.

> 
> And I think it's worth to spend a comment inside the dts on how to deal
> with SCIF UARTs without clocks, as you need some custom kernel patch for
> your inmate.

There is that nice new board setup document - maybe add it there.

Jan

> 
> Thanks,
>   Ralf
> 
> On 11/16/2017 04:09 PM, [email protected] wrote:
>> From: Jan von Wiarda <[email protected]>
>>
>> - Fix CI build failure introduced by non-existent header file
>> - Changes on cell configs regarding clock usage
>> - Setup debug console correctly
>>
>> Jan von Wiarda (3):
>>   arm-common: Make sure debug console is setup correctly
>>   configs: Updated cell configs for Renesas RZ/G1E (emCON-RZ/G1E from
>>     emtrion)
>>   configs: Updated cell configs for Renesas RZ/G1M (emCON-RZ/G1M from
>>     emtrion)
>>
>>  configs/dts/inmate-emtrion-emconrzg1e.dts | 280 
>> ------------------------------
>>  configs/dts/inmate-emtrion-emconrzg1m.dts | 275 
>> -----------------------------
>>  configs/emtrion-rzg1e-linux-demo.c        |   9 +-
>>  configs/emtrion-rzg1e-uart-demo.c         |   9 +-
>>  configs/emtrion-rzg1e.c                   |   4 +-
>>  configs/emtrion-rzg1m-linux-demo.c        |   9 +-
>>  configs/emtrion-rzg1m-uart-demo.c         |   9 +-
>>  configs/emtrion-rzg1m.c                   |   4 +-
>>  hypervisor/arch/arm-common/uart-hscif.c   |   7 +
>>  9 files changed, 15 insertions(+), 591 deletions(-)
>>


-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to