From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Haowei Cheng(Harvey)" <harvey.cheng@fibocom.com>
Cc: "chunfeng.yun@mediatek.com" <chunfeng.yun@mediatek.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回复: 0001-usb-mtu3-fix-panic-in-mtu3_gadget_wakeup.patch
Date: Thu, 7 Nov 2024 06:13:32 +0100 [thread overview]
Message-ID: <2024110735-entertain-parish-7b45@gregkh> (raw)
In-Reply-To: <SEZPR02MB5495A8637098B92CDEBBFC6C8E532@SEZPR02MB5495.apcprd02.prod.outlook.com>
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
next prev parent reply other threads:[~2024-11-07 5:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 17:54 0001-usb-mtu3-fix-panic-in-mtu3_gadget_wakeup.patch Haowei Cheng(Harvey)
2024-11-05 8:41 ` 0001-usb-mtu3-fix-panic-in-mtu3_gadget_wakeup.patch Greg Kroah-Hartman
2024-11-06 19:39 ` 回复: 0001-usb-mtu3-fix-panic-in-mtu3_gadget_wakeup.patch Haowei Cheng(Harvey)
2024-11-07 5:13 ` Greg Kroah-Hartman [this message]
2024-11-07 5:14 ` Greg Kroah-Hartman
2024-11-07 7:47 ` 回复: " Haowei Cheng(Harvey)
2024-11-07 8:14 ` Greg Kroah-Hartman
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=2024110735-entertain-parish-7b45@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chunfeng.yun@mediatek.com \
--cc=harvey.cheng@fibocom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
/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 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).