archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Greg KH <>
Cc: "" <>
Subject: Re: 5.14.14+ USB regression caused by "usb: core: hcd: Add support for deferring roothub registration" series
Date: Thu, 4 Nov 2021 09:50:12 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

aOn 04.11.21 08:04, Greg KH wrote:
> On Thu, Nov 04, 2021 at 07:53:37AM +0100, Thorsten Leemhuis wrote:
>> On 03.11.21 10:02, Hans de Goede wrote:
>>> We (Fedora) have been receiving multiple reports about USB devices stopping
>>> working starting with 5.14.14 .
>>> An Arch Linux user has found that reverting the first 2 patches from this series:
>>> Fixes things (the 3th patch is just some mostly unrelated refactoring/cleanup).
>>> See here for the Arch-linux discussion surrounding this:
>>> And here are 2 Fedora bug reports of Fedora users being unable to use their
>>> machines due their mouse + kbd not working:
>>> Can we get this patch-series reverted from the 5.14.y releases please ?
>> #regzbot ^introduced: b7a0a792f864583207c593b50fd1b752ed89f4c1
>> #regzbot ignore-activity
> Process question.  Is there anything I need to do here when this is
> resolved?  I'm thinking of reverting the offending patches in 5.16-rc1,
> but when/if that happens, how will the regzbot know this?

You don't need to do something special, but you need to do something ;-)
Regzbot will know the regression got resolved if the commit message of
the fix (a proper one or a revert) in mainline links to the report with
a Link: tag. Hence, the commit should have something like this:


This is something you and many other developers often do already -- and
something that submitting-patches.rst since a few days states

But even if you forget that: As a regression tracker I still have an eye
on things and likely would tell regzbot about it myself, *if* I notice
the fix/revert got merged (and if not, I might send a quick 'hey' what's
up here' mail, which will be a bit annoying for the involved parties,
but that's how it is).

Side note: regbot will even notice if a patch with above Link-Tag gets
posted to one of the mainline list and link to it.

That afaics answered the question, but TWIMC: this report created some
challenges for me/regzbot due to two aspects:

1) the report specifies two commits as culprit
2) the problematic changes are in mainline, 5.15.y and 5.14.y, and I'm
unsure as of now how to handle such situations

For the first aspect I for now settled on "well, just mentioned the
second of the two commits, that's good enough for regzbot, the details
are in the report anyway".

I'm ignoring the second aspect for now and told regzbot only about the
commit in mainline, as my focus for regzbot is on mainline. I guess to
handle this properly, it would be possible to enhance regzbot and then
tall it about 807ac762afee (that's the backport of b7a0a792f864 to 5.14)
as well. But you and Sasha afaics handle things like this already quite
well afaics. But if that would make your life easier, just let me know,
than I'll put it higher on my todo list.

Ciao, Thorsten

  reply	other threads:[~2021-11-04  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-11-04  6:53 ` 5.14.14+ USB regression caused by "usb: core: hcd: Add support for deferring roothub registration" series Thorsten Leemhuis
2021-11-04  7:04   ` Greg KH
2021-11-04  8:50     ` Thorsten Leemhuis [this message]
2021-11-05  7:56       ` Greg KH
2021-11-06  9:26         ` Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 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).