09:27 phasta: If we'd need 2ab510e63197360945f915dd5631a77c63ac6b27 from drm-misc-fixes in drm-misc-next, what would the process be like?
09:39 sima: mlankhorst, tzimmermann mripard ^^
09:40 sima: phasta, ping drm-misc maintainers
09:40 tzimmermann: phasta, easiest would be a backmerge into drm-misc-next on Monday
09:43 phasta: tzimmermann: will that take place on Monday in any case?
09:44 tzimmermann: phasta, it happens when someone asks for it. such as you do now
09:45 tzimmermann: we could also cherry-pick now into drm-misc-next, but we try to avoid that as it has negative side effects
09:46 tzimmermann: that fix will be in upstream on monday and from there we can backmerge into drm-next->drm-misc-next. that's the easiest unless that commit fixes an absolutely critical bug
09:58 phasta: tzimmermann: nope, no hurries, sounds wonderful. If it lands in misc-next some time next week that'd be perfectly fine. Thank you :)
10:47 tzimmermann: mripard: https://paste.opensuse.org/pastes/726d719f3b55 seen on drm-misc-next. fallout from the create_state changes?
12:13 mareko: does using AI for self code review to find typos during development require AI assist disclosure? if we do that for all our commits, do we note AI assist in all of them? wouldn't that make the AI assist tag have much broader meaning?
12:16 karolherbst: personally I'd draw the line at decision making, if it's purely technical review it's probably not adding any value to disclose it, because a static linter acts similar, just less good? For me for reviews it helps to know whether the person made the decision because they dug through the specs or something to come to the conclusion or whether they
12:16 karolherbst: just relied on an AI for that, because I was running into cases where people relied on AI too much there and then got confused about what the spec actually requires
12:34 mripard: tzimmermann: which tree are you building?
12:35 mripard: amdgpu_dm_crtc_reset_state isn't in drm-misc-next, could it be a conflict resolution gone wrong?
12:35 tzimmermann: mriprd, drm-misc-next with allmodconfig
12:35 tzimmermann: i would assume that the trees aren't synced yet (?)
12:36 tzimmermann: it's just the test case that fails BTW
12:45 mripard: yeah but git grep amdgpu_dm_crtc_reset_state drm-misc-next-2026-09-17 returns 0 for me
12:58 mareko: karolherbst: just using it for typos leads to the eventual realization that it's actually crazy good at finding complex incorrect behavior, and then the person fixes it, but AI discovered it
12:59 karolherbst: right.. it's difficult to draw a line between "flaws in the code structure" and "deep understanding of the technical documents"
14:34 tzimmermann: mripard, my bad. that build was on drm-tip
17:20 Lyude: Looks like there's a drm-tip rebuild error, if no one else gets to it I'll have it fixed in a moment
17:36 zmike: fuck you, pipe_tess_spacing.
17:42 Lyude: Is anyone from AMD around who could take a look at this?
18:12 agd5f: Lyude, fixed
18:12 Lyude: awesome!
18:12 Lyude: thanks for the help
18:25 Lyude: hah, now it's broken again but it's my fault this time :). will have it fixed in a sec
18:28 agd5f: Lyude, there's also a silent conflict in the intel-for-CI merge. Needs this patch https://paste.centos.org/view/01e894c0
18:29 agd5f: I can push that once you resolve the new one
18:39 Lyude: gotcha, should have the new one resolved in just a sec
18:45 Lyude: agd5f: done