From: Paul Cercueil <paul@crapouillou.net>
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
Subject: Re: [PATCH] ASoC: dapm: Don't use prefix for regulator name
Date: Mon, 07 Nov 2022 09:52:24 +0000 [thread overview]
Message-ID: <C32ZKR.QZWY19EUAOMQ3@crapouillou.net> (raw)
In-Reply-To: <166680764848.867857.6473365992161385316.b4-ty@kernel.org>
Hi Mark,
Le mer. 26 oct. 2022 à 19:07:28 +0100, Mark Brown <broonie@kernel.org>
a écrit :
> 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
Small reminder that this is a fix for a bug introduced in -rc1, so it
should be queued for the next RC.
Cheers,
-Paul
> 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
next prev parent reply other threads:[~2022-11-07 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 15:01 Paul Cercueil
2022-10-26 18:07 ` Mark Brown
2022-11-07 9:52 ` Paul Cercueil [this message]
2022-11-07 12:57 ` Mark Brown
2022-11-07 13:01 ` Paul Cercueil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C32ZKR.QZWY19EUAOMQ3@crapouillou.net \
--to=paul@crapouillou.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®