[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165236476384.1016627.11149997612368396008.b4-ty@kernel.org>
Date: Thu, 12 May 2022 15:12:43 +0100
From: Mark Brown <broonie@...nel.org>
To: tanureal@...nsource.cirrus.com, lgirdwood@...il.com,
perex@...ex.cz, james.schulman@...rus.com,
rf@...nsource.cirrus.com, oder_chiou@...ltek.com, tiwai@...e.com,
zheyuma97@...il.com, david.rhodes@...rus.com
Cc: linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
patches@...nsource.cirrus.com
Subject: Re: [PATCH 0/6] ASOC: Fix the error handling code of the probe
On Tue, 10 May 2022 23:32:45 +0800, Zheyu Ma wrote:
> These drivers mishandle the regulator resource in the probe function,
> failing to disable the regulator for probing failure.
>
> Zheyu Ma (6):
> ASoC: cs42l52: Fix the error handling of cs42l56_i2c_probe()
> ASoC: cs35l36: Fix the error handling of cs35l36_i2c_probe()
> ASoC: rt5645: Fix the error handling of rt5645_i2c_probe()
> ASoC: tas571x: Fix the error handling of tas571x_i2c_probe()
> ASoC: tas6424: Fix the error handling of tas6424_i2c_probe()
> ASoC: wm8903: Fix the error handling of wm8903_i2c_probe()
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/6] ASoC: cs42l52: Fix the error handling of cs42l56_i2c_probe()
commit: c1ce4ba5021a9730c00bab6f8122702deb69d37e
[2/6] ASoC: cs35l36: Fix the error handling of cs35l36_i2c_probe()
commit: cf7250e95d309ae518918613fb904a4565ffc85d
[3/6] ASoC: rt5645: Fix the error handling of rt5645_i2c_probe()
commit: 7883c193d7ae1ccc20ee4c06d2a1fea40074e454
[4/6] ASoC: tas571x: Fix the error handling of tas571x_i2c_probe()
commit: ef1878fd0cd61f0f3fafdf518bb8f1df742ef760
[5/6] ASoC: tas6424: Fix the error handling of tas6424_i2c_probe()
commit: 68cacb5cf5cf04aaa95be1fd76eff728dfddc613
[6/6] ASoC: wm8903: Fix the error handling of wm8903_i2c_probe()
commit: 83d1b65d4cbe6fb0bbdacc18c1f4ad0450275d8f
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
Powered by blists - more mailing lists