Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: olteanv@gmail.com, kishon@kernel.org,
	andriy.shevchenko@linux.intel.com,
	 Haotian Zhang <vulab@iscas.ac.cn>
Cc: linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] phy: hisilicon: hi3670: Fix OF node and device reference leaks
Date: Sun, 13 Sep 2026 16:26:36 +0530	[thread overview]
Message-ID: <178929699677.215437.6593754684719636000.b4-ty@kernel.org> (raw)
In-Reply-To: <20260219163843.1571-1-vulab@iscas.ac.cn>


On Fri, 20 Feb 2026 00:38:43 +0800, Haotian Zhang wrote:
> hi3670_pcie_get_resources_from_pcie() leaks two references:
> 1) The OF node returned by of_get_child_by_name() is never released.
> 2) The device returned by bus_find_device_by_of_node() is never put.
> 
> Fix both leaks by calling of_node_put() right after
> bus_find_device_by_of_node(), and put_device() after dev_get_regmap()
> when the temporary pcie_dev reference is no longer needed.
> 
> [...]

Applied, thanks!

[1/1] phy: hisilicon: hi3670: Fix OF node and device reference leaks
      commit: 2638a0e60f65e38bbd28400340ab92fa67b562b3

Best regards,
-- 
~Vinod



-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

      parent reply	other threads:[~2026-09-13 10:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  6:22 [PATCH] phy: hisilicon: Fix OF node reference leak Haotian Zhang
2026-02-16  8:43 ` Vladimir Oltean
2026-02-16  9:09   ` Andy Shevchenko
2026-02-16  9:11     ` Andy Shevchenko
2026-02-19 16:38 ` [PATCH v2] phy: hisilicon: hi3670: Fix OF node and device reference leaks Haotian Zhang
2026-08-12 13:26   ` Manivannan Sadhasivam
2026-09-13 10:56   ` Vinod Koul [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=178929699677.215437.6593754684719636000.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=kishon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=olteanv@gmail.com \
    --cc=vulab@iscas.ac.cn \
    /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