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:     cychiang@chromium.org, chrome-platform@lists.linux.dev,
        linmq006@gmail.com, Liam Girdwood <lgirdwood@gmail.com>,
        tzungbi@google.com, Takashi Iwai <tiwai@suse.com>,
        groeck@chromium.org, linux-kernel@vger.kernel.org,
        bleung@chromium.org, Jaroslav Kysela <perex@perex.cz>,
        alsa-devel@alsa-project.org
In-Reply-To: <20220602114529.6303-1-linmq006@gmail.com>
References: <20220602114529.6303-1-linmq006@gmail.com>
Subject: Re: [PATCH] ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe
Message-Id: <165459875534.301808.8602571934037682831.b4-ty@kernel.org>
Date:   Tue, 07 Jun 2022 11:45:55 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 2 Jun 2022 15:45:29 +0400, Miaoqian Lin wrote:
> of_parse_phandle() returns a node pointer with refcount
> incremented, we should use of_node_put() on it when not need anymore.
> Add missing of_node_put() to avoid refcount leak.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe
      commit: 0a034d93ee929a9ea89f3fa5f1d8492435b9ee6e

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