mbox series

[0/2] ASoC: mt8183: Fixes from an initial glance at a kselftest run

Message ID 20230224-asoc-mt8183-quick-fixes-v1-0-041f29419ed5@kernel.org (mailing list archive)
Headers show
Series ASoC: mt8183: Fixes from an initial glance at a kselftest run | expand

Message

Mark Brown Feb. 26, 2023, 12:49 p.m. UTC
This is a collection of fixes I came up after glancing through an
initial test run with the snappily named Kukui Jacuzzi SKU16 Chromebook
on KernelCI.  There are more issues flagged, this is just what I fixed
thus far.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
      ASoC: mt8183: Remove spammy logging from I2S DAI driver
      ASoC: mt8183: Fix event generation for I2S DAI operations

 sound/soc/mediatek/mt8183/mt8183-dai-i2s.c | 21 +++------------------
 1 file changed, 3 insertions(+), 18 deletions(-)
---
base-commit: d2980d8d826554fa6981d621e569a453787472f8
change-id: 20230224-asoc-mt8183-quick-fixes-ccb7c567c755

Best regards,

Comments

Mark Brown Feb. 28, 2023, 6 p.m. UTC | #1
On Sun, 26 Feb 2023 12:49:55 +0000, Mark Brown wrote:
> This is a collection of fixes I came up after glancing through an
> initial test run with the snappily named Kukui Jacuzzi SKU16 Chromebook
> on KernelCI.  There are more issues flagged, this is just what I fixed
> thus far.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: mt8183: Remove spammy logging from I2S DAI driver
      commit: d71ed1c8f0f458ae6852fdab055790fe1d9d19b6
[2/2] ASoC: mt8183: Fix event generation for I2S DAI operations
      commit: 18f51ed09888c8e48bd377d1715d4ff807b4c805

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