mbox series

[v2,0/2] ASoC: mediatek: mt8173: Fix error paths

Message ID 20230612-mt8173-fixup-v2-0-432aa99ce24d@chromium.org (mailing list archive)
Headers show
Series ASoC: mediatek: mt8173: Fix error paths | expand

Message

Ricardo Ribalda June 12, 2023, 9:05 a.m. UTC
ASoC: mediatek: mt8173, presented a couple of error paths errors, lets
fix them.

Signed-off-by: Ricardo Ribalda Delgado <ribalda@chromium.org>
---
Changes in v2:
- Fix other error paths bugs, Thanks Dan!
- Link to v1: https://lore.kernel.org/r/20230612-mt8173-fixup-v1-1-81f5c90316d1@chromium.org

---
Ricardo Ribalda Delgado (2):
      ASoC: mediatek: mt8173: Fix snd_soc_component_initialize error path
      ASoC: mediatek: mt8173: Fix irq error path

 sound/soc/mediatek/mt8173/mt8173-afe-pcm.c | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)
---
base-commit: 858fd168a95c5b9669aac8db6c14a9aeab446375
change-id: 20230612-mt8173-fixup-bc602a96dbad

Best regards,

Comments

Mark Brown June 12, 2023, 5:26 p.m. UTC | #1
On Mon, 12 Jun 2023 11:05:30 +0200, Ricardo Ribalda Delgado wrote:
> ASoC: mediatek: mt8173, presented a couple of error paths errors, lets
> fix them.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: mediatek: mt8173: Fix snd_soc_component_initialize error path
      commit: a46d37012a5be1737393b8f82fd35665e4556eee
[2/2] ASoC: mediatek: mt8173: Fix irq error path
      commit: f9c058d14f4fe23ef523a7ff73734d51c151683c

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