mbox series

[0/2] ASoC: soc-core: tidyup error handling for rtd

Message ID 87tuotxlen.wl-kuninori.morimoto.gx@renesas.com
Headers show
Series ASoC: soc-core: tidyup error handling for rtd | expand

Message

Kuninori Morimoto March 30, 2021, 5:25 a.m. UTC
Hi Mark

These are small clanup patches for soc-core.
[1/2] patch adds missing explanation, and
[2/2] patch fixup error handling of rtd.

Kuninori Morimoto (2):
  ASoC: soc-core: add comment for rtd freeing
  ASoC: soc-core: use device_unregister() if rtd allocation failed

 sound/soc/soc-core.c | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

Comments

Mark Brown April 1, 2021, 10:16 a.m. UTC | #1
On 30 Mar 2021 14:25:52 +0900, Kuninori Morimoto wrote:
> These are small clanup patches for soc-core.
> [1/2] patch adds missing explanation, and
> [2/2] patch fixup error handling of rtd.
> 
> Kuninori Morimoto (2):
>   ASoC: soc-core: add comment for rtd freeing
>   ASoC: soc-core: use device_unregister() if rtd allocation failed
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: soc-core: add comment for rtd freeing
      commit: f1b3ee789f4b7a41ad93ff42d4efbae607622ae7
[2/2] ASoC: soc-core: use device_unregister() if rtd allocation failed
      commit: 5fa7553dcd83c576c589fd3e617dc599e4fe15dc

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