From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Zeeshan Ahmad <zeeshanahmad022019@gmail.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: qcom: simplify error check in dwc3_qcom_find_num_ports()
Date: Wed, 25 Feb 2026 00:10:39 +0000 [thread overview]
Message-ID: <20260225001036.gg2ghnayekrhbcxh@synopsys.com> (raw)
In-Reply-To: <20260224064409.3888-1-zeeshanahmad022019@gmail.com>
On Tue, Feb 24, 2026, Zeeshan Ahmad wrote:
> Hi Thinh,
>
> Thank you for the suggestion. I have audited the modern
> drivers/usb/dwc3/dwc3-qcom.c driver on the latest usb-next branch
> and confirmed that it contains the same redundant IRQ error checks.
>
> I will drop the previous patch for the legacy driver and submit a
> new patch targeting the main dwc3-qcom driver shortly.
>
Hi Zeeshan,
Sure. Could you also keep some relevant context from the previous email
thread in your reply? This will help us follow the conversation more
easily.
Thanks,
Thinh
next prev parent reply other threads:[~2026-02-25 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 11:01 [PATCH] usb: dwc3: qcom: simplify error check in dwc3_qcom_find_num_ports() Zeeshan Ahmad
2026-02-19 22:55 ` Thinh Nguyen
2026-02-20 8:15 ` Dan Carpenter
2026-02-21 10:41 ` Zeeshan Ahmad
2026-02-24 0:41 ` Thinh Nguyen
2026-02-24 6:44 ` Zeeshan Ahmad
2026-02-25 0:10 ` Thinh Nguyen [this message]
2026-02-25 6:42 ` [PATCH v2] " Zeeshan Ahmad
2026-02-25 6:51 ` [PATCH v3] " Zeeshan Ahmad
2026-02-26 2:14 ` Thinh Nguyen
-- strict thread matches above, loose matches on Subject: below --
2026-02-24 7:32 [PATCH] " Zeeshan Ahmad
2026-02-25 0:06 ` Thinh Nguyen
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=20260225001036.gg2ghnayekrhbcxh@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=zeeshanahmad022019@gmail.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