[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM=9txsYE1zFDW+ehHQv138DoeT1Fw6hfzfPa4czvXGSjefjw@mail.gmail.com>
Date: Thu, 4 Aug 2022 13:37:37 +1000
From: Dave Airlie <airlied@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@...ll.ch>,
dri-devel <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 5.20/6.0
On Thu, 4 Aug 2022 at 13:16, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Wed, Aug 3, 2022 at 7:46 PM Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > I think I have it resolved, am still doing a full build test, and will
> > then compare against what your suggested merge is.
>
> Hmm.
>
> I end up with *almost* the same thing.
>
> Except I ended up with a
>
> select DRM_BUDDY
>
> for the DRM_AMDGPU config entry, and you don't have that.
>
> I *think* my version is correct, in that clearly the amdgpu driver now
> uses that buddy logic (just doing a random "grep drm_buddy_block" to
> see).
Actually I did miss that so that looks good.
>
> But this was messy enough to resolve that I think people should
> double-check my end, and maybe I just got confused at some point in
> the process.
>
> And while I seem to have gotten the same result as you did on the i915
> firmware side too, again, I'd like people to re-verify.
I'll pull it down and look over it.
Dave.
Powered by blists - more mailing lists