00:26 rodrigovivi: airlied: v2 sent with signoffs fixed and plus 2 more patches as explained there: https://lore.kernel.org/dri-devel/ZYIzv1PK6OljqvGV@intel.com/T/#u
00:26 rodrigovivi: I hope this works now, but if you have any issue please let me know so I change it today still
00:29 rodrigovivi: range-diff between the PRs: https://paste.centos.org/view/92e7706f
01:31 bl4ckb0ne: emersion: i can give you an a-b fwiw
10:53 jfalempe: javierm, it looks like patchwork is down, https://patchwork.freedesktop.org gives error 500
10:55 daniels: jfalempe: patchwork is extremely down, no ETA for return currently
10:59 jfalempe: daniels, ok thanks. I think I can still push a fix to drm-misc-fixes, without the patchwork link with dim.
11:19 javierm: jfalempe: maybe you can manually add links to the kernel.org patchwork? https://patchwork.kernel.org/project/dri-devel/list/
11:20 javierm: at least to have that info in the patches you are going to push
11:22 jfalempe: javierm, thanks, yes I'll try do add the link to kernel patchwork instead.
11:56 jani: jfalempe: you can still add links to the fdo patchwork even if they don't work *right now*
11:57 javierm: indeed, that's true too
11:57 jani: and dim adds them automatically anyway
12:18 jfalempe: jani, I think that works only if you download the patch from patchwork and apply it with dim ?
12:19 jani: jfalempe: nope, just piping the patch to 'dim apply-branch' does the trick
12:20 jfalempe: I got this warning, and no link in the commit message: dim: WARNING: No message-id found in the patch file.
12:22 jfalempe: Hum, I think I should use the mbox patch, not a git patch and that should work.
12:24 javierm: jfalempe: yes, with a mbox patch it does work AFAIK
12:25 jfalempe: yes that works thanks ;)