On Wed, Jul 21, 2021 at 12:15:12PM +0200, Javier Martinez Canillas wrote: > On 7/21/21 12:07 PM, Thomas Zimmermann wrote: > > Hi > > > > Am 21.07.21 um 07:09 schrieb Javier Martinez Canillas: > > ... > >>> > >>> Can I simply put the patches in to drm-misc-next? There was some talk > >>> about a topic branch? > >>> > >> > >> ... which AFAIU means that there's no need for a topic branch, since the > >> patches will be present in linux-next. And the EFI folks can use that to > >> check if there are any integration issues or regressions caused by these. > > > > Merged into drm-misc-next. > > > > Thanks a lot Thomas for all your help! Yeah topic branch makes sense when we have further work that will build on top of a patch sets in at latest _two_ different subsystems, and it doesn't make sense to just merge it all in one place (because too much work, or a refactoring that's too invasive and will cause random conflicts with subsequent work in the same subsystem, or ...). Otherwise just acks and then merge in one place. We shouldn't do bureaucratics like topic branches if there's not an actual need for them. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
