Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     linmq006@gmail.com, linux-kernel@vger.kernel.org,
        b38343@freescale.com, lgirdwood@gmail.com
In-Reply-To: <20220511113506.45185-1-linmq006@gmail.com>
References: <20220511113506.45185-1-linmq006@gmail.com>
Subject: Re: [PATCH] regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt
Message-Id: <165229357360.325561.18079537190408256583.b4-ty@kernel.org>
Date:   Wed, 11 May 2022 19:26:13 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 11 May 2022 15:35:05 +0400, Miaoqian Lin wrote:
> of_node_get() returns a node with refcount incremented.
> Calling of_node_put() to drop the reference when not needed anymore.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt
      commit: afaa7b933ef00a2d3262f4d1252087613fb5c06d

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark