03:44lumag: imre, could you please ping jani regarding the LTTPR patchset? I'd really like to understand if we merge only the first patch through drm-misc or if we merge the whole series?
03:44lumag: Lyude, ^^ same question for nouveau bits
03:45lumag: for the reference: https://lore.kernel.org/dri-devel/20250203-drm-dp-msm-add-lttpr-transparent-mode-set-v5-0-c865d0e56d6e@linaro.org/
04:57digetx: uriah: re stuttering, try qemu patch mentioned here https://lore.kernel.org/qemu-devel/f58d250d-3831-4ff1-a018-f62f9aeb2527@collabora.com/T/#m17ac72336d28a64c793d4e4e0c87fc7dff9aa847
04:58digetx: on guest you should use 6.14 kernel, on host 6.13
04:59uriah: digetx: thanks! can i use 6.14 on both, or will it mess things up?
04:59digetx: you can
05:00uriah: ok
05:01uriah: are there just too many fixes/pstches to chase after in 6.14 to backport to 6.13 for guest?
05:01uriah: patches*
05:06digetx: no, they are new features, not fixes
05:07uriah: ah ok
05:07uriah: stuff other than the top commits in your linux git repo, then?
05:08uriah: i guess i should simplify the work i want to do
05:12digetx: yes
05:12digetx: my git patches only needed for crosvm, not for qemu
05:13digetx: 6.14 has all needed for qemu
05:15uriah: ah ok
05:15uriah: thanks for your answers :)
05:16digetx: np
07:24tzimmermann: sima, airlied, hi. could i have v6.14-rc4 in drm-next, so that i can backmerge into drm-misc-next? thanks
07:37airlied: tzimmermann: it seems to merge cleanly and I think it helps with another merge
07:38airlied:crosses my fingers tip has done it's job and it actually builds
07:38tzimmermann: airlied, thanks a lot
07:39airlied: tzimmermann: okay pushed it out
07:39tzimmermann: thanks
07:40sima: airlied, sometimes I'm scared about tip doing its job :-P
07:43airlied:is doing usual builds in background :-)
11:30jani: lumag: sorry for being awol a bit, it's fine, ack
11:30jani: fine either way
11:38lumag: jani, ack.
11:38lumag: thanks
11:40lumag: dakr, ping?
12:57dakr: lumag, feel free to merge the nouveau one, ack
15:59alyssa: Is anyone planning to do a real review on !33722?
16:00alyssa: marek acked but given it touches the whole tree, I'd like to give people time
16:00alyssa: otoh it will accumulate conflicts fast
16:04glehmann: I was halfway through the diff of the main commit, then gitlab's UI gave up
16:06alyssa: ;;
16:06alyssa: appending .patch to an MR's URL gives you plain text
16:07glehmann: yeah that's what I did
16:08alyssa: :+1:
16:23lumag: dakr, thanks!
17:52cmarcelo: eric_engestrom: what's next step with -> https://gitlab.freedesktop.org/mesa/deqp-runner/-/merge_requests/86
19:22alyssa: glehmann: should I marge? or wait more?
19:28glehmann: there isn't really a reason to wait other than the 24h rule I guess
19:32alyssa: fair
22:39alyssa: what are people using for fossil stats on non-anv/radv?
22:39alyssa: i think i've seen nvk statistics floating around at least..
22:39alyssa: to compare the .csv's I mean
22:42alyssa: yeah https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33306 has nvk fossils
22:43alyssa: not seeing anything for ir3
22:43alyssa: I guess https://gitlab.freedesktop.org/mesa/shader-db/-/issues/1 might be my task for tomorrow then