On 31/05/2023 08:30, Bagas Sanjaya wrote: >> +appropriate time later. Most importantly, any incompatible changes should be >> +clearly pointed out in the patch description and pull request, along with the >> +expected impact on existing users, such as bootloaders or other operating >> +systems. >> + >> +Driver Branch Dependencies >> +~~~~~~~~~~~~~~~~~~~~~~~~~~ >> + >> +A common problem is synchronizing changes between device drivers and devicetree >> +files, even if a change is compatible in both directions, this may require >> +coordinating how the changes get merged through different maintainer trees. >> + >> +Usually the branch that includes a driver change will also include the >> +corresponding change to the devicetree binding description, to ensure they are >> +in fact compatible. This means that the devicetree branch can end up causing >> +warnings in the "make dtbs_check" step. If a devicetree change depends on >> +missing additions to a header file in include/dt-bindings/, it will fail the >> +"make dtbs" step and not get merged. > > Sounds like passing `make dtbs` is a merging requirement. And why shouldn't be? Best regards, Krzysztof
