09:03 austriancoder: valentine: got the kernel working on an armhf target too :)
10:31 biju: Hi all, Just want to check the process for applying a patch in drm-misc-fixes is same as drm-misc-next?
10:31 biju: ./maintainer-tools/dim checkout drm-misc-fixes
10:31 biju: apply the patch (../maintainer-tools/dim b4-shazam)
10:32 biju: ./maintainer-tools/dim push-branch drm-misc-fixes
10:33 biju: Basically I want to merge a patch in drm-misc-fixes as there is a brakage on 7.0-rc1 [1] https://lore.kernel.org/all/20260227015216.2721504-1-chris.brandt@renesas.com/
10:50 javierm: biju: yes, the process you mentioned is correct
10:51 biju: javierm: Thank you
13:29 MoeIcenowy: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40155 created a dirty MR (assumed dirty by me because of hardcoding private const from Zink)
13:29 MoeIcenowy: anyone can raise any better ideas?
17:21 glehmann: looks like r300 is the last driver to use util_framebuffer_init, is there still someone knowledgeable enough about the driver to resolve that?
17:22 glehmann: and if not, can the -Wdeprecated-declarations warning for it be removed?
17:23 anholt: tbh I think we should prohibit use of deprecated-declarations warnings.
19:49 airlied: anholt: agree, Linus is right about introducing warnings isn't going to make anyone fix it, it's just annoying for everyone
22:07 CounterPillow: alternate suggestion: if there's one user left, and said user is a legacy driver nobody really wants to work on, just copy the function into the user and be done with it.
22:11 airlied: yes but the person doing the work should just do it instead of adding deprecated warnings
22:11 CounterPillow: Yeah