On Wed, 26 Jun 2019 at 15:29, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > > Hi Emil. > > > > > > > Thanks, > > > patch applied to drm-misc-next and will be pushed out soon. > > > > > Isn't an ack/rb from a DT maintainer a requirement before being picked > > via the DRM trees? > > It used to be a thing, although it could have changed recently. > I got OK via irc to take some simple panel bindings patches. > Which explains the lack of a-b or r-b on this patch from any DT folks. > > So I processed what was in queue. > Maybe the OK was only for a smaller set of patches but I did process > only panel-bindings that I was ready to add my r-b on. > Fair enough. I've seen people add the "ok" in the commit itself and the line ending with "# over IRC" or alike. > > > > AFAICT there are no users for this binding, yet I'm not sure if that > > is a requirement. > To my best knowledge a kernel user is not a requirement. > In this case there is a patch in-the-works and I considered to > wait until the patch was ready. But decided to process the DT-binding > as the binding is a prerequisite for the panel driver, > but not the other way around. Again to my understanding. > > So everything was done to avoid having panel patches hanging in > dri-devel for excessive amount of time. > One could say that this was already the case that they had waited for > too long. > > Another - not so obvious thing . was that having all patches in > drm-misc-next allows us to have an easier time migrating all panel > patches to yaml which I hope will take place in the next month or two. > I am waiting for the inital patch-set by Rob to land, and then there > is some janitorial job to migrate remainign panel bindings to yaml. > This is easier to do with everyting in drm-misc-next rather than asking > several different persons to do it. > Once done there will be lot of examples to work from, so for new panel > bindings it should be easier. > Ooh shiny. Thanks Sam. -Emil P.S. From a non-native speaker to another, spell check FTW. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
