#asahi-dev · 2021-12-02 15:08
arnd_some subsystem maintainers prefer the binding changes to go in with the driver, obviously I don't care if I merge both branches anyway#asahi-dev · 2021-12-02 15:07
arnd_marcan: that is usually the easiest way, the alternatives are to have the dt binding patch first, using the same commit for both branches, or to do it over more than one merge window#asahi-dev · 2021-12-02 14:45
arnd_obviously any added features may only become available once both branches are merged#asahi-dev · 2021-12-02 14:45
arnd_the idea is that each half should be regression-free and tested without the other half, to ensure that there are no incompatible binding changes#asahi-dev · 2021-12-02 14:44
arnd_marcan: yes, all the DT changes should come together, separately from the driver changes#asahi-dev · 2021-12-02 14:08
arnd_marcan: send it to soc@kernel.org, but separately from the DT changes#asahi-dev · 2021-12-01 14:48
arnd_maz: ah, I missed that thread, thanks for pointing it out. Replied by email now.#asahi-dev · 2021-12-01 14:29
arnd_right#asahi-dev · 2021-12-01 14:25
arnd_dt fixes are usually for stuff that caused a regression or that was clearly wrong (e.g. incorrect numbers). We sometimes add missing devices in early bugfixes as well, but only if there is a good reason and it's still early during the cycle.#asahi-dev · 2021-12-01 14:23
arnd_marcan: we only add new machines for the next release, so v5.17