linux-kernel - Re: [PATCH v2 0/5] Add support for SOF on i.MX8M

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, 16 Apr 2020 00:36:40 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Daniel Baluta <daniel.baluta@....nxp.com>
Cc:     Daniel Baluta <daniel.baluta@....com>,
        ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com,
        devicetree@...r.kernel.org, alsa-devel@...a-project.org,
        festevam@...il.com, robh+dt@...nel.org,
        linux-kernel@...r.kernel.org, pierre-louis.bossart@...ux.intel.com,
        shengjiu.wang@....com, linux-imx@....com
Subject: Re: [PATCH v2 0/5] Add support for SOF on i.MX8M

On Thu, 9 Apr 2020 10:18:27 +0300, Daniel Baluta wrote:
> From: Daniel Baluta <daniel.baluta@....com>
> 
> This patch series adds support for SOF on i.MX8M family. First board
> from this family that has a DSP is i.MX8MP.
> 
> First 2 patches are trying to fix some compilation issues, the next two
> are adding the imx8m support and the last one adds the devicetree
> binding.
> 
> [...]

Applied, thanks!

[1/5] ASoC: SOF: imx8: Fix randbuild error
      commit: fe17e6cdc0fefca96ba9659be4b2b07487cbf0c5
[2/5] ASoC: SOF: imx: fix undefined reference issue
      commit: cb0312f61c3e95c71ec8955a94d42bf7eb5ba617
[3/5] ASoC: SOF: imx: Add i.MX8M HW support
      commit: afb93d716533ddef20fc70e626f7b43f204cb411
[4/5] ASoC: SOF: Add i.MX8MP device descriptor
      commit: 58825cc2253986ec3a4d0d67b8b4dc30945afb52
[5/5] dt-bindings: dsp: fsl: Add fsl,imx8mp-dsp entry
      commit: 35a0f242520520dfa1e8eaf66f20d297b12e413e

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