Re: drm pull for v5.3-rc1

2019-08-07 Thread Matthew Wilcox
On Wed, Aug 07, 2019 at 03:30:38PM +0100, Steven Price wrote: > On 07/08/2019 15:15, Matthew Wilcox wrote: > > On Tue, Aug 06, 2019 at 11:40:00PM -0700, Christoph Hellwig wrote: > >> On Tue, Aug 06, 2019 at 12:09:38PM -0700, Matthew Wilcox wrote: > >>> Has anyone looked at turning the interface ins

Re: drm pull for v5.3-rc1

2019-07-15 Thread Linus Torvalds
On Mon, Jul 15, 2019 at 12:36 PM Thomas Hellström (VMware) wrote: > > - I've never had any kernel code more reviewed than this. Hmm. It may have been reviewed, but that wasn't visible in the commits themselves, so when I look at the pull request, I don't see that. > - The combined callback / arg

Re: DRM pull for v5.3-rc1

2019-07-15 Thread Daniel Vetter
On Mon, Jul 15, 2019 at 7:57 PM Jason Gunthorpe wrote: > > On Mon, Jul 15, 2019 at 07:53:06PM +0200, Daniel Vetter wrote: > > > > So, I'll put it on a topic and send you two a note next week to decide > > > if you want to merge it or not. I'm really unclear how nouveau's and > > > AMD's patchflow

Re: DRM pull for v5.3-rc1

2019-07-15 Thread Daniel Vetter
On Mon, Jul 15, 2019 at 5:04 PM Jason Gunthorpe wrote: > > On Mon, Jul 15, 2019 at 04:19:26PM +0200, Daniel Vetter wrote: > > > > Linus, do you have any advice on how best to handle sharing mm > > > patches? The hmm.git was mildly painful as it sits between quilt on > > > the -mm side and what see

Re: DRM pull for v5.3-rc1

2019-07-15 Thread Jason Gunthorpe
On Mon, Jul 15, 2019 at 04:19:26PM +0200, Daniel Vetter wrote: > > Linus, do you have any advice on how best to handle sharing mm > > patches? The hmm.git was mildly painful as it sits between quilt on > > the -mm side and what seems like 'a world of interesting git things' > > on the DRM side (bu

Re: DRM pull for v5.3-rc1

2019-07-15 Thread Daniel Vetter
On Mon, Jul 15, 2019 at 2:29 PM Jason Gunthorpe wrote: > > [urk, html email.. forgive the mess] > > On Mon, Jul 15, 2019 at 04:59:39PM +1000, Dave Airlie wrote: > > > VMware had some mm helpers go in via my tree (looking back I'm > > not sure Thomas really secured enough acks on these, b