linux-kernel - Re: [PATCH] ASoC: dapm: Don't use prefix for regulator name

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <166680764848.867857.6473365992161385316.b4-ty@kernel.org>
Date:   Wed, 26 Oct 2022 19:07:28 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Paul Cercueil <paul@...pouillou.net>,
        Takashi Iwai <tiwai@...e.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH] ASoC: dapm: Don't use prefix for regulator name

On Tue, 25 Oct 2022 16:01:49 +0100, Paul Cercueil wrote:
> When a component has a prefix, and uses a SND_SOC_DAPM_REGULATOR_SUPPLY,
> the name of the regulator should not use the prefix, otherwise it won't
> be properly matched in the DT/ACPI.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: dapm: Don't use prefix for regulator name
      commit: 1683d3282f240336a2b4b6b541d435facfe8bbb6

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