From: Thorsten Leemhuis <email@example.com> To: Greg KH <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: Regression: plugging in USB scanner breaks all USB functionality Date: Sat, 4 Dec 2021 11:26:45 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <Yas83rCCAQcabahe@kroah.com> On 04.12.21 11:03, Greg KH wrote: > On Fri, Dec 03, 2021 at 06:24:52PM +0100, Thorsten Leemhuis wrote: >> On 02.12.21 16:13, Thorsten Leemhuis wrote: >>> Hi, this is your Linux kernel regression tracker speaking. >>> >>> Thanks for the report. >>> >>> Top-posting for once, to make this easy accessible to everyone. >>> >>> FWIW, 5.14 is EOL, so it might not be fixed there. As the problem is in >>> newer kernels as well, I suspect that it was a change applies to 5.15 or >>> 5.16 that got backported. Maybe one of the developers might have an idea >>> which commit causes it. If that's not the case you likely should try a >>> bisection to find the culprit. Performing one between v5.14.11..v5.14.14 >>> is likely the easiest and quickest way to find it. >>> >>> 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 v5.14.11..v5.14.14 >>> #regzbot title usb: plugging in USB scanner breaks all USB functionality >>> [regression present in 5.15.2 und 5.16-rc3, too] >>> #regzbot ignore-activity >> >> #regzbot introduced ff0e50d3564f >> #regzbot fixed-by 385b5b09c3546c87cfb730b76abe5f8d73c579a2 > > Odd, where did that git commit id come from? I don't see it in > linux-next or Linus's tree. > > confused, Yeah, sorry, after sending that mail it occurred to me that this wasn't ideal and hard to follow. I got it from here: https://email@example.com/ I already decided that next time something like this comes up I'll reply to the mail with the details instead (with proper quoting) to make this easier to follow. Reading that message again I suspect that I might have been a bit quick as well, as this might not be the commit id this ends up with when it gets merged: I now see that this is likely a developers tree and not one that gets indirectly merged. Sorry, I'll manually keep an eye on things to fix this up once that patch gets its real it. Ciao, Thorsten BTW, while at it: #regzbot monitor https://firstname.lastname@example.org/
next prev parent reply other threads:[~2021-12-04 10:26 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-02 14:55 Robert Munteanu 2021-12-02 15:13 ` Thorsten Leemhuis 2021-12-03 17:24 ` Regression: plugging in USB scanner breaks all USB functionality #forregzbot Thorsten Leemhuis 2021-12-04 10:03 ` Greg KH 2021-12-04 10:26 ` Thorsten Leemhuis [this message] 2021-12-04 10:44 ` Regression: plugging in USB scanner breaks all USB functionality Greg KH 2021-12-04 11:06 ` Thorsten Leemhuis 2021-12-02 15:17 ` Greg Kroah-Hartman 2021-12-03 15:33 ` Robert Munteanu 2021-12-03 10:57 ` Mathias Nyman 2021-12-03 11:36 ` Takashi Iwai 2021-12-03 16:22 ` Robert Munteanu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Regression: plugging in USB scanner breaks all USB functionality' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).