Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     nfraprado@collabora.com
Cc:     matthias.bgg@gmail.com, devicetree@vger.kernel.org,
        krzysztof.kozlowski+dt@linaro.org, jiaxin.yu@mediatek.com,
        angelogioacchino.delregno@collabora.com,
        linux-kernel@vger.kernel.org, shane.chien@mediatek.com,
        linux-mediatek@lists.infradead.org, lgirdwood@gmail.com,
        linux-arm-kernel@lists.infradead.org, alsa-devel@alsa-project.org,
        robh+dt@kernel.org, kernel@collabora.com, tzungbi@google.com
In-Reply-To: <20220429203039.2207848-1-nfraprado@collabora.com>
References: <20220429203039.2207848-1-nfraprado@collabora.com>
Subject: Re: [PATCH 0/3] Add missing dt-binding properties for audio components on mt8192-asurada
Message-Id: <165211666198.1065748.1151009730882312510.b4-ty@kernel.org>
Date:   Mon, 09 May 2022 18:17:41 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 29 Apr 2022 16:30:36 -0400, Nícolas F. R. A. Prado wrote:
> These patches add properties that were missing on the dt-bindings of the
> audio components used by mt8192-asurada. Namely the i2s-share
> properties for the sound platform and the #sound-dai-cells on the
> rt1015p and rt5682 codecs when they're referenced by the machine sound
> node.
> 
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: dt-bindings: mediatek: mt8192: Add i2s-share properties
      commit: e056cf4341ae3f856f1e38da02b27cb04de4c69b
[2/3] ASoC: dt-bindings: rt1015p: Add #sound-dai-cells
      commit: 2f45536587e53a7a22024e12fbe97ef13598e623
[3/3] ASoC: dt-bindings: rt5682: Add #sound-dai-cells
      commit: 0adccaf1eac91a2c2ee6a54a6de042affe9860f4

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