linux-kernel - Re: [PATCH 1/2] ASoC: qcom: sc8280xp: set card driver name from match data

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]

Message-Id: <170169323312.40199.10496089708040196942.b4-ty@kernel.org>
Date:   Mon, 04 Dec 2023 12:33:53 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Banajit Goswami <bgoswami@...cinc.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
        linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH 1/2] ASoC: qcom: sc8280xp: set card driver name from
 match data

On Fri, 01 Dec 2023 14:53:31 +0100, Krzysztof Kozlowski wrote:
> Sound machine drivers for all newer Qualcomm SoC platforms are the
> exactly same, therefore it makes sense to use same machine driver for
> newer platforms as well.  Choice of sound topology and user-space Alsa
> UCM files depends however on card driver name, which must be customized
> per each board.  Allow such customization by using driver match data as
> sound card driver name.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: qcom: sc8280xp: set card driver name from match data
      commit: 625ed9457de50d7726ccb3f2bc4e01e543ceb126
[2/2] ASoC: qcom: sc8280xp: Add support for SM8450 and SM8550
      commit: fdcaecfc71e2f4ab70ce9469f14dd64c23bf401a

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