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'm fine if the sub-components are picked up first (and land in next > first), but the MFD binding picked up first is a problem usually. And > that has happened multiple times. Also, it does mean the MFD branch > will have binding warnings, but that's Lee's problem if he cares > (probably not). Linus complained about picking up the subcomponents without the core, especially if the MFD doesn't end up landing in the same release for whatever reason (which is fair enough, especially when the MFD does miss).
Attachment:
signature.asc
Description: PGP signature
