linux-kernel - Re: [PATCH v2] ASoC: fsl: Add missing error handling in pcm030_fabric

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164338551779.1711238.6752613705973183003.b4-ty@kernel.org>
Date:   Fri, 28 Jan 2022 15:58:37 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Eric Millbrandt <emillbrandt@...aresearch.com>,
        Miaoqian Lin <linmq006@...il.com>, alsa-devel@...a-project.org,
        Jaroslav Kysela <perex@...ex.cz>,
        Liam Girdwood <lgirdwood@...il.com>,
        Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH v2] ASoC: fsl: Add missing error handling in pcm030_fabric_probe

On Thu, 27 Jan 2022 13:13:34 +0000, Miaoqian Lin wrote:
> Add the missing platform_device_put() and platform_device_del()
> before return from pcm030_fabric_probe in the error handling case.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: fsl: Add missing error handling in pcm030_fabric_probe
      commit: fb25621da5702c104ce0a48de5b174ced09e5b4e

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