Daniel Leung
Daniel Leung
#48428 does not work correctly. For example, if you add revision for `qemu_x86`, `qemu_x86_64` would then be interpreted as `qemu_x86@64`.
If you add a dummy file `qemu_x86_64.conf`, `qemu_x86@64` would be valid due to the directory scanning code. Another example is that, if you add `qemu_x86_tiny_1.conf`, a board `[email protected]` would appear.
#48798 is merged.
Please roll [drivers: uart_xmc4xxx: Reindent after previous commit](https://github.com/zephyrproject-rtos/zephyr/pull/48540/commits/40825d82458c75e6cf57f0757b829236d5c25298) and [drivers: uart_xmc4xxx: Improve code readability](https://github.com/zephyrproject-rtos/zephyr/pull/48540/commits/af502c8552b0c6f27a53967f07893e3e2bf234b6) into previous commits. They can be considered part of the first commits introducing those changes.
Please rebase first.
Errr.. the error said to increase `CONFIG_MAX_THREAD_BYTES`.
Wonder if `subsys/testsuite/{arch,board,soc}` should be moved down one level. It looks weird if `arch`, `board` and `soc` appear alongside `coverage` and `ztest`.
> > Wonder if `subsys/testsuite/{arch,board,soc}` should be moved down one level. It looks weird if `arch`, `board` and `soc` appear alongside `coverage` and `ztest`. > > Good question, although i'm...
Ah... I thought the unit_testing board would appear in the general board list. In that case, I think we can go with the current location.
Test failure is to due to some timing issue on QEMU and `qemu_cortex_a53` which is unrelated to this change.