From: Zijun Hu <zijun_hu@icloud.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Kory Maincent <kory.maincent@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Justin Chen <justin.chen@broadcom.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Simon Horman <horms@kernel.org>
Cc: Zijun Hu <zijun_hu@icloud.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Zijun Hu <quic_zijuhu@quicinc.com>
Subject: [PATCH net 0/2] net: Fix 2 OF device node refcount leakage issues
Date: Thu, 12 Dec 2024 23:06:53 +0800 [thread overview]
Message-ID: <20241212-drivers_fix-v1-0-a3fbb0bf6846@quicinc.com> (raw)
This patch series is to fix 2 OF device node refcount leakage issues.
Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
---
Zijun Hu (2):
net: pse-pd: tps23881: Fix device node refcount leakage in tps23881_get_of_channels()
net: bcmasp: Fix device node refcount leakage in bcmasp_probe()
drivers/net/ethernet/broadcom/asp2/bcmasp.c | 1 +
drivers/net/pse-pd/tps23881.c | 1 +
2 files changed, 2 insertions(+)
---
base-commit: ff7afaeca1a15fbeaa2c4795ee806c0667bd77b2
change-id: 20241206-drivers_fix-735f56ed5ec7
Best regards,
--
Zijun Hu <quic_zijuhu@quicinc.com>
next reply other threads:[~2024-12-12 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 15:06 Zijun Hu [this message]
2024-12-12 15:06 ` [PATCH net 1/2] net: pse-pd: tps23881: Fix device node refcount leakage in tps23881_get_of_channels() Zijun Hu
2024-12-12 15:06 ` [PATCH net 2/2] net: bcmasp: Fix device node refcount leakage in bcmasp_probe() Zijun Hu
2024-12-12 15:33 ` [PATCH net 0/2] net: Fix 2 OF device node refcount leakage issues Kory Maincent
2024-12-13 10:50 ` Zijun Hu
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=20241212-drivers_fix-v1-0-a3fbb0bf6846@quicinc.com \
--to=zijun_hu@icloud.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=horms@kernel.org \
--cc=justin.chen@broadcom.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=quic_zijuhu@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
all inboxes | Powered by JetHome®