From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, regressions@lists.linux.dev,
michal.pecio@gmail.com, Yiyu Zhou <yiyu@yiyuzhou.io>,
Dennis Wissel <dennis@dsine.de>
Subject: Re: [PATCH v2] xhci: give back TDs and clean up ep0 after disconnect
Date: Fri, 30 Oct 2026 13:05:16 +0200 [thread overview]
Message-ID: <f362a385-e1d6-437c-a31c-fbf4414fa0f5@linux.intel.com> (raw)
In-Reply-To: <2026103009-handful-labored-d1ce@gregkh>
On 10/30/26 07:22, Greg KH wrote:
> On Thu, Oct 29, 2026 at 10:43:24PM +0200, Mathias Nyman wrote:
>> From: Yiyu Zhou <yiyu@yiyuzhou.io>
>>
>> Fix a regression in v7.3 introduced by the commits in the Fixes tags.
>> Those patches avoid endpoint recovery and rapid state changes after
>> the root port link is lost.
>>
>> This caused a regression in device enumeration.
>
> I see this patch twice?
>
My mistake, bash history shows I added the same file twice after git send-email
> And sashiko seems to object to it, is that response correct?
>
It does find one potential case where this patch does not fix the enumeration
of devices that disconnect during reset.
This patch however is tested and does resolve the two real life regressions
where devices briefly disconnect during enumeration.
There's a risk for more real life regression if I too hastily fix this patch
to cover that sashiko case.
Thanks
Mathias
next prev parent reply other threads:[~2026-10-30 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 20:43 [PATCH v2] xhci: give back TDs and clean up ep0 after disconnect Mathias Nyman
2026-10-29 20:43 ` Mathias Nyman
2026-10-29 22:08 ` sashiko-bot
2026-10-30 5:22 ` Greg KH
2026-10-30 11:05 ` Mathias Nyman [this message]
2026-10-30 12:05 ` Michal Pecio
2026-10-30 16:57 ` Mathias Nyman
2026-10-30 19:27 ` Michal Pecio
2026-10-29 22:11 ` sashiko-bot
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=f362a385-e1d6-437c-a31c-fbf4414fa0f5@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=dennis@dsine.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=yiyu@yiyuzhou.io \
/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.