linux-kernel - Re: [PATCH] ASoC: da7219: Fix I/O voltage range configuration during probe

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: <159802798182.25503.9768924803803430146.b4-ty@kernel.org>
Date:   Fri, 21 Aug 2020 17:39:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
        Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Support Opensource <support.opensource@...semi.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: da7219: Fix I/O voltage range configuration during probe

On Fri, 21 Aug 2020 15:22:59 +0100, Adam Thomson wrote:
> Previous improvements around handling device and codec level
> probe functionality added the possibility of the voltage level
> being undefined for the scenario where the IO voltage retrieved
> from the regulator supply was below 1.2V, whereas previously the
> code defaulted to the 2.5V to 3.6V range in that case. This
> commit restores the default value to avoid this happening.

Applied to

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

Thanks!

[1/1] ASoC: da7219: Fix I/O voltage range configuration during probe
      commit: fcea8b023a5f06ea0180ae65b01520b0414ee325

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