[TLDR: This mail in primarily relevant for Linux regression tracking. A change or fix related to the regression discussed in this thread was posted or applied, but it did not use a Link: tag to point to the report, as Linus and the documentation call for. Things happen, no worries -- but now the regression tracking bot needs to be told manually about the fix. See link in footer if these mails annoy you.] On 03.02.23 13:46, Linux kernel regression tracking (#adding) wrote: > On 01.02.23 14:32, Paul Cercueil wrote: >> Hi Sascha, Greg, >> >> I have a breakage in 6.2-rc* that I eventually bisected to this commit, >> on a Ingenic SoC (using the jz4740 musb driver) with ECM or RNDIS >> configured through gadgetfs. >> >> When plugging the board to my PC, the USB network interface is >> recognized, but 'ip link' sees it as 'NO-CARRIER'. With this commit >> reverted on v6.2-rc5, everything works fine. > > [CCing the regression list, as it should be in the loop for regressions: > https://docs.kernel.org/admin-guide/reporting-regressions.html] > > Thanks for the report. To be sure the issue doesn't fall through the > cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression > tracking bot: > > #regzbot ^introduced 321b59870f850 > #regzbot title usb: gadget: USB network interface is recognized, but 'ip > link' sees it as 'NO-CARRIER' > #regzbot ignore-activity #regzbot fix: bb07bd68fa0983e3915 #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you. #regzbot ignore-activity
