[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024110735-entertain-parish-7b45@gregkh>
Date: Thu, 7 Nov 2024 06:13:32 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Haowei Cheng(Harvey)" <harvey.cheng@...ocom.com>
Cc: "chunfeng.yun@...iatek.com" <chunfeng.yun@...iatek.com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: 回复:
0001-usb-mtu3-fix-panic-in-mtu3_gadget_wakeup.patch
On Wed, Nov 06, 2024 at 07:39:59PM +0000, Haowei Cheng(Harvey) wrote:
> Hi greg k-h,
>
> We found during development that when there are data packets to be sent on the USB RNDIS network card,
> unplugging the USB cable will trigger a certain probability of system warning or panic.
> We observed that the mtu3_gadget_wakeup function uses the usleep_range_state function,
> which has certain scenario limitations. Therefore, we made this optimization.
Please do not top-post :(
Just resend your patch properly, in a format that we can apply it in,
and we will be glad to review and discuss it that way.
Look for thousands of examples on the lists for how to do this, as well
as the documentation in the kernel tree itself which explains this in
way-too-much detail.
thanks,
greg k-h
Powered by blists - more mailing lists