From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Huang Wei <huangwei@kylinos.cn>
Cc: Minas Harutyunyan <hminas@synopsys.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc2: debugfs: fix memory leak of hsotg->regset
Date: Wed, 2 Sep 2026 11:25:24 +0200 [thread overview]
Message-ID: <2026090200-mothproof-snowplow-f443@gregkh> (raw)
In-Reply-To: <20260902090541.2134430-1-huangwei@kylinos.cn>
On Wed, Sep 02, 2026 at 05:05:41PM +0800, Huang Wei wrote:
> Hi,
>
> Gentle ping on this one. It's a small debugfs memory leak fix that
> mirrors the equivalent dwc3 fix (commit e6bdf8195b4a ("usb: dwc3: fix
> memory leak of dwc->regset")). Happy to address any feedback or resend
> if needed.
I have 700+ USB patches still to process, it's in the queue...
To help out, please help review other patches!
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-02 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 10:04 [PATCH] usb: dwc2: debugfs: fix memory leak of hsotg->regset Huang Wei
2026-09-02 9:05 ` Huang Wei
2026-09-02 9:25 ` Greg Kroah-Hartman [this message]
2026-09-03 6:44 ` Huang Wei
2026-09-05 1:00 ` 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=2026090200-mothproof-snowplow-f443@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=huangwei@kylinos.cn \
--cc=linux-kernel@vger.kernel.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