From: Pelle Windestam <pelle@windestam.se>
To: "Prashanth K" <prashanth.k@oss.qualcomm.com>,
胡连勤 <hulianqin@vivo.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Jon Hunter" <jonathanh@nvidia.com>
Cc: "mwalle@kernel.org" <mwalle@kernel.org>,
"quic_jjohnson@quicinc.com" <quic_jjohnson@quicinc.com>,
David Brownell <dbrownell@users.sourceforge.net>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"opensource.kernel" <opensource.kernel@vivo.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Brad Griffis <bgriffis@nvidia.com>,
Harshit Mogalapalli <harshit.m.mogalapalli@gmail.com>
Subject: Re: 答复: [PATCH v3] usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null
Date: Thu, 6 Feb 2025 08:47:30 +0100 [thread overview]
Message-ID: <4735da72-63b7-4168-974c-ac4681d69a1e@windestam.se> (raw)
In-Reply-To: <33a19657-a890-4d59-b7ea-5798cf8f7d9b@oss.qualcomm.com>
> Are you also using tegra-xudc ? ep_disable routine may be called in an
> atomic (interrupt) context.
Nope, I have a board based on a NXP iMX7D CPU, I'm not 100% sure what
the tegra-xudc equivalent would be for that.
//Pelle
prev parent reply other threads:[~2025-02-06 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYUPR06MB621733B5AC690DBDF80A0DCCD2042@TYUPR06MB6217.apcprd06.prod.outlook.com>
2025-01-16 13:11 ` [PATCH v3] usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null Jon Hunter
2025-01-16 13:28 ` gregkh
2025-01-16 15:01 ` Jon Hunter
2025-01-17 5:04 ` 答复: " 胡连勤
2025-01-17 8:24 ` gregkh
2025-01-17 9:48 ` Jon Hunter
2025-01-21 12:19 ` Jon Hunter
2025-01-23 14:56 ` Dan Carpenter
2025-02-05 6:38 ` 答复: " 胡连勤
2025-02-05 19:29 ` Pelle Windestam
2025-02-06 2:36 ` 答复: " 胡连勤
2025-02-06 4:24 ` Prashanth K
2025-02-06 7:47 ` Pelle Windestam [this message]
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=4735da72-63b7-4168-974c-ac4681d69a1e@windestam.se \
--to=pelle@windestam.se \
--cc=bgriffis@nvidia.com \
--cc=dan.carpenter@linaro.org \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@gmail.com \
--cc=hulianqin@vivo.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=prashanth.k@oss.qualcomm.com \
--cc=quic_jjohnson@quicinc.com \
/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