[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159542547441.19620.1737685462805157717.b4-ty@kernel.org>
Date: Wed, 22 Jul 2020 14:44:44 +0100
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org,
Daniel Baluta <daniel.baluta@....nxp.com>
Cc: festevam@...il.com, linux-kernel@...r.kernel.org,
linux-imx@....com, shengjiu.wang@....com
Subject: Re: [PATCH 0/7] SOF IMX fixes
On Mon, 20 Jul 2020 10:20:39 +0300, Daniel Baluta wrote:
> This patchseries contains a couple of SOF IMX fixes
> found during our first IMX SOF release.
>
> Daniel Baluta (7):
> ASoC: SOF: define INFO_ flags in dsp_ops for imx8
> ASoC: SOF: imx: Use ARRAY_SIZE instead of hardcoded value
> ASoC: SOF: imx8: Fix ESAI DAI driver name for i.MX8/iMX8X
> ASoC: SOF: imx8m: Fix SAI DAI driver for i.MX8M
> ASoC: SOF: imx8: Add SAI dai driver for i.MX/i.MX8X
> ASoC: SOF: topology: Update SAI config bclk/fsync rate
> ASoC: SOF: pcm: Update rate/channels for SAI/ESAI DAIs
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: SOF: define INFO_ flags in dsp_ops for imx8
commit: 45b7262174dcc2ca62e23220219eee1462dcada9
[2/7] ASoC: SOF: imx: Use ARRAY_SIZE instead of hardcoded value
commit: beaa7bd10dce348b033aff3f466ab1a78b33fed3
[3/7] ASoC: SOF: imx8: Fix ESAI DAI driver name for i.MX8/iMX8X
commit: bcba2c9d62f391cd2cd6acb7f658d47bfb10e8b9
[4/7] ASoC: SOF: imx8m: Fix SAI DAI driver for i.MX8M
commit: f23a8e9402f899e3555ac8aff3d3d050adafe39e
[5/7] ASoC: SOF: imx8: Add SAI dai driver for i.MX/i.MX8X
commit: 68f56f618c3fbc4b1af0428f715f952cdada7a54
[6/7] ASoC: SOF: topology: Update SAI config bclk/fsync rate
commit: 72bb9564fd97cd4f6dec88c8363acc3ab642673f
[7/7] ASoC: SOF: pcm: Update rate/channels for SAI/ESAI DAIs
commit: 51b0243aefaa554ca57817562da8eb269280d4ae
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
Powered by blists - more mailing lists