On Sun, Jan 16, 2022 at 4:21 AM Thorsten Leemhuis <regressions@xxxxxxxxxxxxx> wrote: > > [TLDR: I'm adding this regression to regzbot, the Linux kernel > regression tracking bot; most text you find below is compiled from a few > templates paragraphs some of you might have seen already.] > > Hi, this is your Linux kernel regression tracker speaking. > > Adding the regression mailing list to the list of recipients, as it > should be in the loop for all regressions, as explained here: > https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html > > On 14.01.22 11:56, Charles Keepax wrote: > > Hi guys, > > > > My Zynq based board stopped booting today, a bisect points to this > > patch: > > > > commit 0f153a1b8193 ("usb: chipidea: Set the DT node on the child device") > > Thanks for the report. > > To be sure this issue doesn't fall through the cracks unnoticed, I'm > adding it to regzbot, my Linux kernel regression tracking bot: > > #regzbot ^introduced 0f153a1b8193 > #regzbot title usb: chipidea: Zynq based board stopped booting today > #regzbot ignore-activity > > Reminder: when fixing the issue, please add a 'Link:' tag with the URL > to the report (the parent of this mail) using the kernel.org redirector, 'kernel.org redirector' is lore.kernel.org? It would be clearer to just say that. > as explained in 'Documentation/process/submitting-patches.rst'. Regzbot > then will automatically mark the regression as resolved once the fix > lands in the appropriate tree. For more details about regzbot see footer. Would it be possible for you to provide the exact link tag in your reports? That would be easier and less error prone than describing what to do in prose. Rob
