linux-kernel - Re: [PATCH v2 0/2] Introduce sof_of_machine

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>] [day] [month] [year] [list]

Message-Id: <166128061023.1031684.5884182401063110421.b4-ty@kernel.org>
Date:   Tue, 23 Aug 2022 19:50:10 +0100
From:   Mark Brown <broonie@...nel.org>
To:     pierre-louis.bossart@...ux.intel.com,
        peter.ujfalusi@...ux.intel.com, daniel.baluta@....com,
        angelogioacchino.delregno@...labora.com, lgirdwood@...il.com,
        Chunxu Li <chunxu.li@...iatek.com>
Cc:     linux-arm-kernel@...ts.infradead.org, matthias.bgg@...il.com,
        sound-open-firmware@...a-project.org, tinghan.shen@...iatek.com,
        linux-mediatek@...ts.infradead.org,
        project_global_chrome_upstream_group@...iatek.com,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        yc.hung@...iatek.com
Subject: Re: [PATCH v2 0/2] Introduce sof_of_machine_select

On Fri, 5 Aug 2022 15:04:47 +0800, Chunxu Li wrote:
> From: "chunxu.li" <chunxu.li@...iatek.com>
> 
> Change since v1:
>   - remove the callback of_machine_select defined in sof-priv.h
>   - move sof_of_machine_select to common code, and called in
>     sof_machine_check
>   - rename .board field to .compatible in structure snd_sof_of_mach
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: Introduce function sof_of_machine_select
      commit: 6ace85b9838dc0162b474dbbbb6b388e7561f6a7
[2/2] ASoC: SOF: mediatek: Add sof_mt8186_machs for mt8186
      commit: 2dec9e09e955dfc4b7843fa4f9c09e7ee8931b1d

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