mbox series

[0/2] ASoC: Intel: bxt*: Fix regression caused by COMP_DUMMY changes

Message ID 20240108094842.28782-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: Intel: bxt*: Fix regression caused by COMP_DUMMY changes | expand

Message

Peter Ujfalusi Jan. 8, 2024, 9:48 a.m. UTC
Hi,

We just noticed that
13f58267cda3 ("ASoC: soc.h: don't create dummy Component via COMP_DUMMY()")
caused regression (NULL pointer dereference) on GLK machines beacuse the
drivers are using the codec name or dai_name to find the link to apply a fixup.

13f58267cda3 is sent for 6.8, so these patches are going to be needed to be able
to boot these machines.

Regards,
Peter
---
Peter Ujfalusi (2):
  ASoC: Intel: bxt_da7219_max98357a: Fix kernel ops due to COMP_DUMMY
    change
  ASoC: Intel: bxt_rt298: Fix kernel ops due to COMP_DUMMY change

 sound/soc/intel/boards/bxt_da7219_max98357a.c | 6 ++++++
 sound/soc/intel/boards/bxt_rt298.c            | 3 ++-
 2 files changed, 8 insertions(+), 1 deletion(-)

Comments

Mark Brown Jan. 8, 2024, 3:48 p.m. UTC | #1
On Mon, 08 Jan 2024 11:48:40 +0200, Peter Ujfalusi wrote:
> We just noticed that
> 13f58267cda3 ("ASoC: soc.h: don't create dummy Component via COMP_DUMMY()")
> caused regression (NULL pointer dereference) on GLK machines beacuse the
> drivers are using the codec name or dai_name to find the link to apply a fixup.
> 
> 13f58267cda3 is sent for 6.8, so these patches are going to be needed to be able
> to boot these machines.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: Intel: bxt_da7219_max98357a: Fix kernel ops due to COMP_DUMMY change
      commit: 59b946ea30806064c4ac78f0ac93642655dd4f2e
[2/2] ASoC: Intel: bxt_rt298: Fix kernel ops due to COMP_DUMMY change
      commit: 3ec71290db4de298b67659ef2bc2a8f84cf9537b

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