Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 07 Nov 2022 09:52:24 +0000
From:   Paul Cercueil <paul@crapouillou.net>
Subject: Re: [PATCH] ASoC: dapm: Don't use prefix for regulator name
To:     Mark Brown <broonie@kernel.org>
Cc:     Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
        Jaroslav Kysela <perex@perex.cz>,
        Takashi Iwai <tiwai@suse.com>,
        Liam Girdwood <lgirdwood@gmail.com>,
        linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Message-Id: <C32ZKR.QZWY19EUAOMQ3@crapouillou.net>
In-Reply-To: <166680764848.867857.6473365992161385316.b4-ty@kernel.org>
References: <20221025150149.113129-1-paul@crapouillou.net>
        <166680764848.867857.6473365992161385316.b4-ty@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Mark,

Le mer. 26 oct. 2022 =E0 19:07:28 +0100, Mark Brown <broonie@kernel.org>=20
a =E9crit :
> On Tue, 25 Oct 2022 16:01:49 +0100, Paul Cercueil wrote:
>>  When a component has a prefix, and uses a=20
>> SND_SOC_DAPM_REGULATOR_SUPPLY,
>>  the name of the regulator should not use the prefix, otherwise it=20
>> won't
>>  be properly matched in the DT/ACPI.
>>=20
>>=20
>=20
> Applied to
>=20
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git=20
> for-next

Small reminder that this is a fix for a bug introduced in -rc1, so it=20
should be queued for the next RC.

Cheers,
-Paul

> Thanks!
>=20
> [1/1] ASoC: dapm: Don't use prefix for regulator name
>       commit: 1683d3282f240336a2b4b6b541d435facfe8bbb6
>=20
> All being well this means that it will be integrated into the=20
> 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.
>=20
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems=20
> and
> send followup patches addressing any issues that are reported if=20
> needed.
>=20
> 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.
>=20
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>=20
> Thanks,
> Mark