On Mon, May 14, 2018 at 12:31 PM, Daniel Vetter daniel@ffwll.ch wrote:
On Mon, May 14, 2018 at 08:10:29AM -0700, Dirk Hohndel wrote:
On Mon, May 14, 2018 at 05:01:43PM +0200, Thomas Hellstrom wrote:
I haven't seen any comments in the week since I wrote this. I'm not familiar with the process for the drm changes - so what are the usual next steps? Do I need to submit all or part of this somewhere else? Or does Dave simply take the series (since it has no executable code changes at all)?
There are a number of teams sending pull requests to Dave. One option would be to have it all go through the drm-misc tree. (CC'ing Daniel Vetter about that). Another option would perhaps be to send a pull request directly to Dave (Dave?) And finally, one option would be to rely on the maintainers of each submodule to take the patches that touch that module. If you go for this last option, I can surely take the patches that touch vmwgfx, and Christian the TTM patches.
Again, since this involves no code changes, I think I'd prefer the path directly via Dave, simply as it makes it more likely that none of them get lost... assuming you are willing to do that, Dave, where would you like that PR?
Cc: dri-devel and send it to Dave and you should be good. But I thought Alex pulled this all in now? In the end probably doesn't matter really if it gets merged twice :-)
Looks like Christian merged the ttm change and that is in my PR today. For the others I think we were running into some issues with merging them in our internal git tree (internal export control stuff) so feel free to send a separate PR for them if you don't want to wait for us to sort out the internal merge first.
Alex
Cheers, Daniel
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel