00:05fdobridge: <karolherbst🐧🦀> I think I should just merge my kernel patch 🙂 it's missing a review though
00:06fdobridge: <karolherbst🐧🦀> ehh push
00:06fdobridge: <gfxstrand> That'd be nice....
00:07fdobridge: <gfxstrand> I don't know that I can review but I'll happily ack/tested-by the shit out of it. 😅
00:13fdobridge: <gfxstrand> Okay, plausible Maxwell run going now...
00:29fdobridge: <airlied> @gfxstrand ping for 242 again 🙂
13:49senatorM: So it's not that much anymore to work, little bit of annotation , some lines, configuring the parameters but heavy testing session, I decided to carry this out, but no new info, cadical and roaring bitmaps are just so good work. They fall under the propagator based solvers. So it's really real method. Foreign hackers from various institutions understood my ideas, and they already had it too though. So don't kill the messenger. We are good, campus from
13:49senatorM: Glasgow coders say real things indeed.
13:57Ermine: karolherbst, airlied: requesting banhammer (this one was banned in #wayland yesterday)
15:33fdobridge: <gfxstrand> It's mostly dispatch indirect. I've started on it but it's annoying because pre-Turing can't multiply on the MME.
18:40fdobridge: <airlied> @gfxstrand okay the nouveau patch on dri-devel, let's see if we can start landing this ship
19:05fdobridge: <gfxstrand> Can you rev the deprecate patch with the right types? I'll RB the new stuff ASAP.
19:33fdobridge: <airlied> just sent it
19:37fdobridge: <karolherbst🐧🦀> btw, I pushed the helper invoc fix, should arrive at stable branches at some point 🙃
19:37fdobridge: <gfxstrand> New UAPI patch is reviewed.
19:39fdobridge: <gfxstrand> RB'd
19:39fdobridge: <gfxstrand> I'm going to build myself a branch and run a test. Here's hoping it doesn't all crash and burn. 😅
19:43fdobridge: <gfxstrand> Where? I don't see it in drm-next or drm-fixes
19:55fdobridge: <karolherbst🐧🦀> drm-misc-fices
19:55fdobridge: <karolherbst🐧🦀> *fixes
21:39airlied: dakr: you can drop the MIT licenses from the files with the SPDX in them, just leave the copyright line, and author line if you want
21:46airlied: dakr: I've sent an r-b along with Faith's, if you are commiting thing to drm-misc-next, could you maybe grab https://patchwork.freedesktop.org/patch/551227/ and apply it just before or just after the series?
22:05fdobridge: <gfxstrand> I'm going to go ahead and pull the UAPI patches into the main NVK MR now.
22:06fdobridge: <gfxstrand> Well, after I've done some rebasing
22:12fdobridge: <gfxstrand> I'm running a `git rebase -x "ninja -C _build install" origin/main` right now
22:44fdobridge: <gfxstrand> Ugh... test machine just went down. 😭
22:45fdobridge: <gfxstrand> Either a fluke or drm-next is somehow less stable. 😕
23:04fdobridge: <gfxstrand> @airlied, dakr: Could one of you pleas @ me here once it's landed and tell me what branch it's sitting in.
23:05airlied: dakr: if you do apply that patch make sure to get your sob on it
23:34fdobridge: <gfxstrand> Rebased on Alyssa's NIR 2.0 MR and running one more CTS run, this time with the new API.
23:50fdobridge: <gfxstrand> @karolherbst @airlied Putting together a blog post FAQ to go out on the Collabor blog tomorrow. Any edits or suggestions for additional questions would be appreciated: https://paste.centos.org/view/aa8ea73b
23:52fdobridge: <airlied> it probably won't be in drm-next until next week
23:52fdobridge: <airlied> Red *H*at
23:53fdobridge: <airlied> https://cgit.freedesktop.org/drm-misc/log/ will be where it start life (drm-next) branch
23:53fdobridge: <airlied> drm-misc-next
23:54fdobridge: <airlied> personally I'd taper back the file issues, to only if you are actively working on improving the driver and want to write patches to fix the issues you file
23:55fdobridge: <gfxstrand> Yeah, let me play with that wording a bit.