01:09 <shadows> any opinions on naming style for compatible of System on Module boards, i.e. there is Milk-V Mars which is an embedded board unto itself, then there are products Milk-V Mars CM and Milk-V Mars CM Lite which are different populated chip configurations of the same thing a Raspberry Pi CM4 compatible module

01:09 <shadows> it was previously milkv-mars-cm and milkv-mars-cm-lite but the Mars CM doesn't have much to do with the Mars

01:10 <shadows> I was thinking maybe milkv-marscm ? instead of milkv-mars-cm

01:10 <shadows> kind of silly to think about this but once it's in and accepted to Linux and U-Boot it's probably not going to change again. Now's a good time to hear some thoughts and get it right

01:13 <shadows> the other related question is whether to name the dts files ...cm-emmc and ..cm-lite to give a hint about the functionality or else stay close to the product names ..cm and ..cm-lite

02:38 <shadows> Tartarus: we discussed committing pending devicetree-rebasing changes to U-Boot, but what about the workflow for development; is there a convenient way to to point to a local Linux source tree in place of U-Boot copy of devicetree-rebasing?

02:40 <shadows> for the moment I'm doing this complicated git rm of dts/upstream/src/riscv/starfive and then making symlinks to the local Linux tree

02:40 <shadows> I would hope it might be something like a compile env variable to point to the tree instead of using devicetree-rebasing

10:50 <Caterpillar> hello, who is the maintainer of https://source.denx.de ? My account has not yet been activated

14:25 <Tartarus> Caterpillar: Did you follow the instructions about sending an email to source-admins AT denx DOT de?

14:25 <Tartarus> shadows: For things not even in devicetree-rebasing under some -rc tag? No, no one has written anything up for that

14:35 <Caterpillar> Tartarus: of course

14:46 <Tartarus> We have had people miss that ;) But then yes, they should get to it soon, if it's been more than a few days, email them your monday or tuesday maybe?