On Tue, May 28, 2024 at 09:03:08PM +0200, Bartosz Golaszewski wrote: > Note: I am resending this series in its entirety once more for > discussions and reviews. If there won't be any major objections, I'll > then start sending individual bits and pieces to appropriate trees. > > Merging strategy: The DT binding and DTS changes are a no-brainer, they > can go through the wireless, regulator and arm-msm trees separately. The > bluetooth and PCI changes have a build-time dependency on the power > sequencing code. The bluetooth changes also have a run-time dependency on > the PCI pwrctl part. In order to get it into next I plan to pick up the > power sequencing code into my own tree and maintain it. I can then > provide an immutable tag for the BT and PCI trees to pull. I wouldn't > stress about the BT runtime dependency as it will be fixed once all > changes are in next. The PCI changes are very self-contained and any conflicts will be trivial, so rather than messing with an immutable tag, how about if I just ack them and you can include them in your tree directly?
