From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Mark Brown <broonie@kernel.org>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, oneukum@suse.com, stable@kernel.org
Subject: Re: [RFT PATCH v2 1/1] usb: hub: Fix flushing and scheduling of delayed work tuning runtime pm
Date: Fri, 27 Jun 2025 18:57:19 +0300 [thread overview]
Message-ID: <e85e2b80-ff3b-43eb-8ec4-cdd0a42339e3@linux.intel.com> (raw)
In-Reply-To: <344dd9c9-07af-4e22-8cf2-1fbd0b4e5869@oss.qualcomm.com>
On 27.6.2025 18.23, Konrad Dybcio wrote:
> On 6/27/25 4:52 PM, Mathias Nyman wrote:
>> On 27.6.2025 17.34, Mark Brown wrote:
>>> On Fri, Jun 27, 2025 at 05:20:44PM +0300, Mathias Nyman wrote:
>>>> Delayed work to prevent USB3 hubs from runtime-suspending immediately
>>>> after resume was added in commit 8f5b7e2bec1c ("usb: hub: fix detection
>>>> of high tier USB3 devices behind suspended hubs").
>>>
>>> This doesn't apply for me against any of mainline, pending-fixes or
>>> -next.
>>
>> Ah, right, -next of course already has version 1 of "usb: hub: Fix
>> flushing and scheduling of delayed work that tunes runtime pm"
>>
>> I'll rebase this patch on top of that
>
> FWIW I applied this one on next-20250624 (not containing the v1 fix)
> and ran some testing, with no issues seen
>
> Tested-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> # SC8280XP CRD
>
That is good news. Thanks Konrad for testing
-Mathias
next prev parent reply other threads:[~2025-06-27 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 14:20 [RFT PATCH v2 0/1] Fix "detection of high tier USB3 devices" patch in usb-linus Mathias Nyman
2025-06-27 14:20 ` [RFT PATCH v2 1/1] usb: hub: Fix flushing and scheduling of delayed work tuning runtime pm Mathias Nyman
2025-06-27 14:34 ` Mark Brown
2025-06-27 14:52 ` Mathias Nyman
2025-06-27 15:10 ` Mark Brown
2025-06-27 15:23 ` Konrad Dybcio
2025-06-27 15:57 ` Mathias Nyman [this message]
2025-06-27 15:19 ` Mark Brown
2025-06-27 16:48 ` Mathias Nyman
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=e85e2b80-ff3b-43eb-8ec4-cdd0a42339e3@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=stable@kernel.org \
--cc=stern@rowland.harvard.edu \
/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.