* Re:[PATCH V2] usb: xhci: Add debugfs support for xHCI port bandwidth
@ 2025-03-04 7:09 raoxu
0 siblings, 0 replies; 2+ messages in thread
From: raoxu @ 2025-03-04 7:09 UTC (permalink / raw)
To: mathias.nyman, gregkh; +Cc: linux-usb, linux-kernel, wangyuli, zhanjun
On 2025/3/3 18:36, greg k-h wrote:
>
>The subject line is very odd, can you please fix that up and resend a v2
>patch?
>
I have sent v2 patch, No code changes were made, only the subject was changed.
thanks,
raoxu
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re:[PATCH V2] usb: xhci: Add debugfs support for xHCI port bandwidth
@ 2025-03-04 12:51 raoxu
0 siblings, 0 replies; 2+ messages in thread
From: raoxu @ 2025-03-04 12:51 UTC (permalink / raw)
To: mathias.nyman, gregkh; +Cc: linux-usb, linux-kernel, wangyuli, zhanjun, raoxu
On 2025/3/4 20:31, Mathias Nyman wrote:
>I do however have some larger rework suggestions to this.
>
>Instead of queuing three commands on one file read, parsing and
>copy the content from each context dma into an array on stack, we could
>have separate files in debugfs for each speed, and queue one command
>for each. we could also skip the array on stack and print values from context
>directly.
>
>Something is also very off with the locks in this patch.
>Looks like every lock/unlock got replaced with an unlock
thanks Mathias Nyman,
Thank you for your valuable suggestions.I will separate files in debugfs for each speed.
skipping the array on stack and print values from context directly sounds good. looks is a error and i will fix it.
According to your suggestion i will send patch v3
thanks,
raoxu
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-03-04 12:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-04 12:51 Re:[PATCH V2] usb: xhci: Add debugfs support for xHCI port bandwidth raoxu
-- strict thread matches above, loose matches on Subject: below --
2025-03-04 7:09 raoxu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox