linux-kernel - Re: [PATCH 1/2] ASoC: qcom: dt-bindings: sm8250: update compatibles

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 29 Oct 2020 16:26:50 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     linux-kernel@...r.kernel.org, robh+dt@...nel.org,
        devicetree@...r.kernel.org, alsa-devel@...a-project.org,
        lgirdwood@...il.com, Rob Herring <robh@...nel.org>
Subject: Re: [PATCH 1/2] ASoC: qcom: dt-bindings: sm8250: update compatibles

On Thu, 29 Oct 2020 10:15:49 +0000, Srinivas Kandagatla wrote:
> Update compatible string as board compatible and device compatible
> should not be same!. New compatible is now suffixed with -sndcard
> to be inline with other Qualcomm Sound cards.
> 
> This also fixes the warnings/error reported by dt_binding_check.

Applied to

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

Thanks!

[1/2] ASoC: qcom: dt-bindings: sm8250: update compatibles
      commit: a889583a19206636082c44625141b26392e46a62
[2/2] ASoC: qcom: sm8250: update compatible with new bindings
      commit: bbc4e1bb5fd6577ed668e7c2ba0705dff1783bce

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