linux-kernel - Re: [PATCH] ASoC: SOF: Introduce function 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>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 05 Sep 2022 16:38:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, angelogioacchino.delregno@...labora.com,
        daniel.baluta@....com, pierre-louis.bossart@...ux.intel.com,
        Chunxu Li <chunxu.li@...iatek.com>,
        peter.ujfalusi@...ux.intel.com
Cc:     sound-open-firmware@...a-project.org,
        linux-arm-kernel@...ts.infradead.org, yc.hung@...iatek.com,
        project_global_chrome_upstream_group@...iatek.com,
        linux-mediatek@...ts.infradead.org, alsa-devel@...a-project.org,
        matthias.bgg@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: SOF: Introduce function sof_of_machine_select

On Sat, 3 Sep 2022 11:21:51 +0800, Chunxu Li wrote:
> From current design in sof_machine_check the SOF can only support
> ACPI type machine.
> 
> In sof_machine_check if there is no ACPI machine exist, the function
> will return -ENODEV directly, that's we don't expected if we do not
> base on ACPI machine.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: Introduce function sof_of_machine_select
      commit: 354f6008b730a217a3e6ad982eda42e90e6f7473

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