03:57 airlied: jani: drm-next has an i915 and a komeda patch to fix building after the header changes I just got in misc
04:18 airlied: oh and one omap
04:29 airlied: jani: you need to allmodconfig those changes a bit harder, with an arm cross compiler :-
04:29 airlied: :-)
06:21 dolphin: demarchi: pull-request-next did break and generates drm-intel-next PR even when I'm in drm-intel-gt-next worktree...
06:21 dolphin: so jani / rodrigovivi, don't wonder about the weird tag
07:14 jani: airlied: damn. I did cross-compile arm and arm64, but not quite allmodconfig :(
07:18 dolphin: airlied: Sent the drm-intel-gt-next PR in one go. Do sync with sima on the topic of the DG2 single CCS fix.
07:19 jani: airlied: huh, I also built with clang, and didn't see the errors you saw. anyway, thanks for cleaning up after me!
07:19 dolphin: airlied: also, Google is bouncing messages to your gmail as spam...
07:19 dolphin: "Gmail has detected that this message is\n5.7.1 likely unsolicited mail. To reduce the amount of spam sent to Gmail,\n5.7.1 this message has been blocked."
07:41 airlied: dolphin: nice, I don't pick up PRs from there so that's fine, I use lore to grab them
09:30 MTCoster: Quick maintainer question - would drm-misc-fixes be the correct target for something like https://lore.kernel.org/dri-devel/489aa9ab-3de1-4bfb-aaae-b093536d16ce@imgtec.com/, or should it go to drm-misc-next and get picked into -fixes if needed?
09:37 dolphin: airlied, sima: There are apparently some potential rebase conflicts to apply the workaround fix to drm-intel-gt-next, so backmerge of drm-next might be in place once you have pulled the PR
09:37 sima:kinda on long w/e
09:37 sima: I guess this one is up to airlied
09:38 dolphin: ah, nevermind then :)
09:38 dolphin: we're not at the point <this is fine burning house meme>, so next week should be fine to resolve, still
09:46 dolphin: airlied_: ^^ did you catch above?
12:58 rodrigovivi: dolphin: No worries. I also generated some bad tag in my last PR because dim broke in the middle. Likely with GitLab branches we will be able to delete the bad tags easily
17:35 Company: zmike: "why the farfalle is this app calling glXInitialize and eglInitialize?"
17:36 Company: zmike: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9989 - GTK goes "oh, this driver can't do transparency with EGL, I better use GLX"
18:12 zmike: 🤕
18:12 zmike: I forgot about that
20:08 jimc: hey all, Id like to take another run at https://patchwork.freedesktop.org/series/125066/ what should I rebase upon to get a clean git am ? would 6.9-rc5 work ?