From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Jiada Wang <jiada_wang@mentor.com>
Subject: Re: [PATCH] ASoC: dpcm: extend channel merging to the backend cpu dai
Date: Thu, 28 Jun 2018 11:15:50 +0100 [thread overview]
Message-ID: <20180628101550.GC14040@sirena.org.uk> (raw)
In-Reply-To: <20180627094818.5885-1-jbrunet@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
On Wed, Jun 27, 2018 at 11:48:18AM +0200, Jerome Brunet wrote:
> As you've probably noticed, this patch applies on top Jiada's patch
> pf4c277b817cc ("ASoC: soc-pcm: DPCM cares BE channel constraint")
That isn't a valid hash...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-06-28 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 9:48 Jerome Brunet
2018-06-28 10:15 ` Mark Brown [this message]
2018-06-28 13:08 ` Jerome Brunet
2018-06-28 10:20 ` Applied "ASoC: dpcm: extend channel merging to the backend cpu dai" 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=20180628101550.GC14040@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jbrunet@baylibre.com \
--cc=jiada_wang@mentor.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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®