From: patchwork-bot+linux-amlogic@kernel.org
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH 0/2] ASoC: meson: fix codec-to-codec link setup
Date: Wed, 29 Apr 2020 00:21:18 +0000 [thread overview]
Message-ID: <158811967871.27675.3059969909036804776.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200420114511.450560-1-jbrunet@baylibre.com>
Hello:
This series was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Mon, 20 Apr 2020 13:45:09 +0200 you wrote:
> This patchset fixes the problem reported by Marc in this thread [0]
> The problem was due to an error in the meson card drivers which had
> the "no_pcm" dai_link property set on codec-to-codec links
>
> [0]: https://lore.kernel.org/r/20200417122732.GC5315@sirena.org.uk
>
> Jerome Brunet (2):
> ASoC: meson: axg-card: fix codec-to-codec link setup
> ASoC: meson: gx-card: fix codec-to-codec link setup
>
> [...]
Here is a summary with links:
- [1/2] ASoC: meson: axg-card: fix codec-to-codec link setup
https://git.kernel.org/khilman/linux-amlogic/c/1164284270779e1865cc2046a2a01b58a1e858a9
- [2/2] ASoC: meson: gx-card: fix codec-to-codec link setup
https://git.kernel.org/khilman/linux-amlogic/c/de911b4e683f9c28a063bb62991f2db206c38ba4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-04-29 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:45 Jerome Brunet
2020-04-20 11:45 ` [PATCH 1/2] ASoC: meson: axg-card: " Jerome Brunet
2020-04-20 11:45 ` [PATCH 2/2] ASoC: meson: gx-card: " Jerome Brunet
2020-04-20 13:36 ` [PATCH 0/2] ASoC: meson: " Mark Brown
2020-04-29 0:21 ` patchwork-bot+linux-amlogic [this message]
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=158811967871.27675.3059969909036804776.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
/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®