All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Robert Munteanu <rombert@apache.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	tiwai@suse.com, regressions@lists.linux.dev,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regression: plugging in USB scanner breaks all USB functionality
Date: Thu, 2 Dec 2021 16:17:27 +0100	[thread overview]
Message-ID: <YajjhwMDkX2CyrQD@kroah.com> (raw)
In-Reply-To: <35f7428b39f996c793f5b4a6a314772681c73d7a.camel@apache.org>

On Thu, Dec 02, 2021 at 03:55:44PM +0100, Robert Munteanu wrote:
> Hi,
> 
> After updating from kernel 5.14.11 to 5.14.14 I am seeing the following
> problem:

Can you run 'git bisect' between those kernel versions to get the
offending commit located?  It shouldn't take that long as there's not a
lot of changes there.

thanks,

greg k-h

  parent reply	other threads:[~2021-12-02 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 14:55 Regression: plugging in USB scanner breaks all USB functionality 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       ` Regression: plugging in USB scanner breaks all USB functionality Thorsten Leemhuis
2021-12-04 10:44         ` Greg KH
2021-12-04 11:06           ` Thorsten Leemhuis
2021-12-05 18:09             ` Regression: plugging in USB scanner breaks all USB functionality #forregzbot Thorsten Leemhuis
2021-12-02 15:17 ` Greg Kroah-Hartman [this message]
2021-12-03 15:33   ` Regression: plugging in USB scanner breaks all USB functionality 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 \
    --in-reply-to=YajjhwMDkX2CyrQD@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=rombert@apache.org \
    --cc=tiwai@suse.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.