On Sun, Sep 07, 2025 at 08:43:32AM -0400, Alyssa Anne Rosenzweig wrote: > > Please do not combine DTS patches in patchsets for Greg (e.g. USB). Greg > > expressed that many times, that he takes all or nothing, and DTS cannot > > go via driver branches/trees. > > >From the cover letter, emphasis mine: > > > With the dwc3 glue driver this series can now also be merged independently > > once it's ready: Patches 1-4 can go through the dwc3 tree, 5-15 through > > tipd, 16-18 should go together through the phy tree, and I'll take the > > DTS changes through my tree. **If everyone's happy with the overall > > approach here I can also just send these as individual series** > That's great, but a major pain in the butt for any maintainer. It would require me to manually pick out the patches to be added to my tree and manually apply them? We have good tools now, b4, that wants to take a whole patch series. And you want me to take a whole patch series, as I can now add the info that is in 00/XX to the "merge point" of a big patch series to preserve the information that is provided here. So you loose out if you that is not preserved in the tree, and you make more work for maintainers to try to sift through just what should, and should not, be taken. Remember, some of us maintainers get 1000+ emails a day to do something with. Our development process is optimized for our most limited resource, maintainers, not developers, sorry. Think about it if you were on the receiving end of this, what would you want to see present for you to be able to review and then apply this to your tree? So please, split patches up into "one series per tree". It's the only sane way for us to work. Yes, it's a pain for platform/dts stuff at times, but for everything else, it works really well. thanks, greg k-h
