On Thu, Jun 29, 2023 at 11:59 AM Mark Brown <broonie@xxxxxxxxxx> wrote: > > On Thu, Jun 29, 2023 at 11:48:34AM -0600, Rob Herring wrote: > > On Thu, Jun 29, 2023 at 10:00 AM Mark Brown <broonie@xxxxxxxxxx> wrote: > > > > That says it's a bit unusual to use a separate branch with a PR, it > > > doesn't say anything about it being the end of the world to pick up > > > parts of a series that are ready without picking up the whole lot, > > > especially when we're getting to the merge window. > > > There's some risk the core part could change affecting the sub > > components after you pick it up, or that the author just abandons > > getting the core part upstream and we're left with a dead driver. > > Right, I'm suggesting applying the core part without waiting for every > single leaf driver to be lined up rather than the other way around - > that way the core part is stable and the leaf drivers only have issues > with changes in their subsystems that they'll have anyway even with > waiting. Leaf drivers can be added on top as they're ready and if > something misses a release then it can go through the subsystem, and if > people do end up wandering off then you've still got whatever did get > merged in case someone else wants to pick things up. I misunderstood. I thought you wanted to apply things to get them out of your queue. That doesn't work when the leaf drivers depend on the core, so what do we do there? A branch or Lee takes everything? That's almost always the case with the bindings as the core binding references the child node bindings. My preference there would be that Lee picks up all the bindings with the core driver. Rob
