Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     lgirdwood@gmail.com, jbrunet@baylibre.com, robh+dt@kernel.org,
        stephan@gerhold.net, Sameer Pujar <spujar@nvidia.com>
Cc:     Mark Brown <broonie@kernel.org>, devicetree@vger.kernel.org,
        alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Fix warning related to 'sound-name-prefix' binding
Date:   Tue, 21 Sep 2021 18:26:59 +0100
Message-Id: <163224493612.45861.17851911764511102643.b4-ty@kernel.org>
In-Reply-To: <1632238860-16947-1-git-send-email-spujar@nvidia.com>
References: <1632238860-16947-1-git-send-email-spujar@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 21 Sep 2021 21:11:00 +0530, Sameer Pujar wrote:
> commit 82d3ec1d89fa ("ASoC: Use schema reference for sound-name-prefix")
> added name-prefix.yaml schema and the same reference was used in couple
> of other schemas. But this is causing following warning and the same is
> fixed in current patch.
> 
>  Documentation/devicetree/bindings/sound/nxp,tfa989x.example.dt.yaml:
>  audio-codec@34: 'sound-name-prefix' does not match any of the regexes:
>  'pinctrl-[0-9]+'
>   From schema: Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
>  Documentation/devicetree/bindings/sound/nxp,tfa989x.example.dt.yaml:
>  audio-codec@36: 'sound-name-prefix' does not match any of the regexes:
>  'pinctrl-[0-9]+'
>   From schema: Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Fix warning related to 'sound-name-prefix' binding
      commit: 013148fe7f5eb420a497e35d9aa8020cdfe92eb6

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