Hi Greg, On Wed, Jan 26, 2022 at 9:20 AM Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Sun, Dec 12, 2021 at 10:48:14AM +0100, Thorsten Leemhuis wrote: > > [TLDR: adding this regression to regzbot; most of this mail is compiled > > from a few templates paragraphs some of you might have seen already.] > > > > Hi, this is your Linux kernel regression tracker speaking. > > > > Top-posting for once, to make this easy accessible to everyone. > > > > Thanks for the report. BTW, if anyone like me wonders what the included > > patch is about: it afaics is the revert of the patch causing the > > problem. Anyway: > > > > 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 70a7f8be8598 > > #regzbot title usb: gadget: atmel: ethernet over USB Gadget not > > recognized anymore after disconnect and reconnect > > #regzbot ignore-activity > > How do I say "this isn't a regression, it's a broken board > configuration" and get regzbot to stop tracking this? I sent the logs to Cristian on Jan, 14, but I don't know if they were helpful. The problem is pretty much reproducible here. I understand that from the previously quoted specification sentence, the hardware must perform VBUS sensing, and this is something I can confirm the hardware is not capable of. But if Cristian cannot reproduce it in a different SOC configured without a VBUS sensing pin, I can only hope Microchip/Atmel will look into the issue. On my side, it seems like I will have to maintain a patched kernel for this hardware. So, let's move on. > thanks, > > greg k-h Best regards, Marcelo.
