mbox series

[0/2] ASoC: Intel: avs: Add support for max98927 codec

Message ID 20220930124538.354992-1-amadeuszx.slawinski@linux.intel.com (mailing list archive)
Headers show
Series ASoC: Intel: avs: Add support for max98927 codec | expand

Message

Amadeusz Sławiński Sept. 30, 2022, 12:45 p.m. UTC
This series adds machine board for max98927 codec present on some
Chromebook devices.

Amadeusz Sławiński (2):
  ASoC: Intel: avs: Add max98927 machine board
  ASoC: Intel: avs: Load max98927 on target platform

 sound/soc/intel/avs/board_selection.c |   8 +
 sound/soc/intel/avs/boards/Kconfig    |  10 ++
 sound/soc/intel/avs/boards/Makefile   |   2 +
 sound/soc/intel/avs/boards/max98927.c | 236 ++++++++++++++++++++++++++
 4 files changed, 256 insertions(+)
 create mode 100644 sound/soc/intel/avs/boards/max98927.c

Comments

Mark Brown Oct. 18, 2022, 11:28 a.m. UTC | #1
On Fri, 30 Sep 2022 14:45:36 +0200, Amadeusz Sławiński wrote:
> This series adds machine board for max98927 codec present on some
> Chromebook devices.
> 
> Amadeusz Sławiński (2):
>   ASoC: Intel: avs: Add max98927 machine board
>   ASoC: Intel: avs: Load max98927 on target platform
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: Intel: avs: Add max98927 machine board
      commit: 1c993300ab1cec9a0a6a3c417614a1d9f35b175b
[2/2] ASoC: Intel: avs: Load max98927 on target platform
      commit: 999ce9967a2f5a64c4bd04ae1edf0a979cf68833

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