linux-kernel - Re: [PATCH v2] ASoC: rt5665: add missed regulator_bulk

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: <169143388818.204874.3565118222220844695.b4-ty@kernel.org>
Date:   Mon, 07 Aug 2023 19:44:48 +0100
From:   Mark Brown <broonie@...nel.org>
To:     oder_chiou@...ltek.com, Zhang Shurong <zhang_shurong@...mail.com>
Cc:     lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ASoC: rt5665: add missed regulator_bulk_disable

On Tue, 01 Aug 2023 23:59:11 +0800, Zhang Shurong wrote:
> The driver forgets to call regulator_bulk_disable()
> 
> Add the missed call to fix it.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: rt5665: add missed regulator_bulk_disable
      commit: c163108e706909570f8aa9aa5bcf6806e2b4c98c

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