Re: Thread for updating minor properties of tracked regressions [consider ignoring it!]

On 3/9/24 11:18, Thorsten Leemhuis wrote:
> Hi! This is the start of a thread I'll use for updating minor properties
> of regressions tracked by regzbot. Consider telling your mailer to
> ignore this thread, the replies are unlikely to be of relevance for you,
> but done here to ensure a public paper trail.
> 
> Interacting with regzbot from arbitrary places is a recently added
> feature of regzbot usable via the new '#regzbot report <url>' command.
> The indented use of this feature is for updating minor aspect of
> regressions already tracked, e.g. "change the title" or "tell regzbot
> about a related discussion". Such things until now had to be done using
> regzbot commands in a direct or indirect reply to report -- but there
> they would mainly be noise for most others and just add to the huge
> amount of mail people already get. It's also takes a more time to send a
> lot of individual mails instead of preparing just one.
> 
> The new command will be documented on
> https://gitlab.com/knurd42/regzbot/ once it got a bit more testing.
> 
> Ciao, Thorsten

#regzbot report:
https://lore.kernel.org/all/[email protected]/
#regzbot introduced: 40d2f5820951dee818d
#regzbot title: drm/i915/backlight: backlight control broken on Thinkpad
T480
#regzbot dup:
https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/16043

#regzbot report:
https://lore.kernel.org/lkml/CADo9pHjr-zZ9C3%2B026y5%[email protected]/
#regzbot introduced: 40d2f5820951dee818d

#regzbot report: https://gitlab.freedesktop.org/drm/amd/-/work_items/5286
#regzbot introduced: 6f71d5dd3206
#regzbot title: drm: amdgpu: handling FreeSync via MCCS broke VRR