I believe it would be better to always use explicit revision in theseOk, so this is anti-social:Yes, that is true. But if you agree, We need to use our latest/greatest SoC/board as the main SoC/Board and rest are with explicit revision in dts/dtb .-dtb-$(CONFIG_ARCH_R8A774A1) += r8a774a1-hihope-rzg2m.dtbThis renames dts away, but at the end of series, new dts is created with the
cases; anything else is fairly confusing, as kernel update breaks your
setup (aka a regresssion).
Now, if -rev2 had few copies, and people really have -rev4, there will
not be much breakage. But imagine if rare -rev5 is released in future...
But mainline already made the choice. I'd just prefer not making same
choice in future.
Now, what to do here? One way would be to apply a series, but add a
README.cip file explaining incompatible change (and any future stuff
people need to know).
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany