On Tue, 15 Feb 2022, Sebastian Andrzej Siewior wrote: > On 2022-02-15 15:16:36 [+0000], Lee Jones wrote: > > On Tue, 15 Feb 2022, Sebastian Andrzej Siewior wrote: > > > > > On 2022-02-15 14:36:01 [+0000], Lee Jones wrote: > > > > Do we really need to coordinate this series cross-subsystem? > > > > > > I would suggest to merge it via irq subsystem but I leave the logistics > > > to tglx. > > > > Could you answer by other questions too please? > > I don't think that I can answer them. I said I leave the logistics to > tglx. > > This can go via one merge via irq. This can also go differently i.e. > feature branch on top of 5.17-rc1 (with 1/7) which is merge into each > subsystem and then the "feature" on top. Apologies for the confusion. I'm not asking you about merge strategies. We can handle that without issue. > Either way it remains bisect-able since each driver is changed > individually. There is no need to merge them in one go but since it is > that small it probably makes sense. But I don't do the logistics here. Okay, this is what I was asking. So there aren't any hard dependencies between the driver changes? Only the drivers are dependent on the API. So, if we choose to do so, we can merge the API and then subsequently add the users one by one into their respective subsystem, in any order. This would save on creating an immutable topic branch which we all pull from. What is your preference Thomas? -- Lee Jones [李琼斯] Principal Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog
