From: Mark Brown <broonie@kernel.org>
To: Olivier Moysan <olivier.moysan@st.com>
Cc: alsa-devel@alsa-project.org, alexandre.torgue@st.com,
linux-kernel@vger.kernel.org, tiwai@suse.com,
lgirdwood@gmail.com, mcoquelin.stm32@gmail.com,
apatard@mandriva.com, perex@perex.cz,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: cs42l51: add dac mux widget in codec routes
Date: Tue, 3 Dec 2019 14:39:09 +0000 [thread overview]
Message-ID: <20191203143909.GL1998@sirena.org.uk> (raw)
In-Reply-To: <20191203141627.29471-1-olivier.moysan@st.com>
[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]
On Tue, Dec 03, 2019 at 03:16:27PM +0100, Olivier Moysan wrote:
> - SND_SOC_DAPM_DAC_E("Left DAC", "Left HiFi Playback",
> - CS42L51_POWER_CTL1, 5, 1,
> - cs42l51_pdn_event, SND_SOC_DAPM_PRE_POST_PMD),
> - SND_SOC_DAPM_DAC_E("Right DAC", "Right HiFi Playback",
> - CS42L51_POWER_CTL1, 6, 1,
> - cs42l51_pdn_event, SND_SOC_DAPM_PRE_POST_PMD),
> + SND_SOC_DAPM_DAC_E("Left DAC", NULL, CS42L51_POWER_CTL1, 5, 1,
> + cs42l51_pdn_event, SND_SOC_DAPM_PRE_POST_PMD),
> + SND_SOC_DAPM_DAC_E("Right DAC", NULL, CS42L51_POWER_CTL1, 6, 1,
> + cs42l51_pdn_event, SND_SOC_DAPM_PRE_POST_PMD),
This looks like an unrelated formatting change?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-03 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 14:16 [PATCH] ASoC: cs42l51: add dac mux widget in codec routes Olivier Moysan
2019-12-03 14:39 ` Mark Brown [this message]
2019-12-03 15:07 ` Olivier MOYSAN
2019-12-09 18:59 ` Applied "ASoC: cs42l51: add dac mux widget in codec routes" to the asoc tree Mark Brown
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=20191203143909.GL1998@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=apatard@mandriva.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@st.com \
--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;
as well as URLs for NNTP newsgroup(s).