From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC_i/iv 3/3] ASoC: Decouple DAPM from CODECs. Part platforms (will be squashed)
Date: Fri, 29 Oct 2010 13:47:26 -0700 [thread overview]
Message-ID: <20101029204725.GF3921@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1288353618-21753-4-git-send-email-jhnikula@gmail.com>
On Fri, Oct 29, 2010 at 03:00:18PM +0300, Jarkko Nikula wrote:
> This patch de-couples DAPM from the CODEC in order for other components to
> have DAPM widgets.
> Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
I suspect this also needs squashing in with the previous patch. If
we're going to split the series it'd be better to split things to move
field by field rather than introduce bisection issues like this.
next prev parent reply other threads:[~2010-10-29 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 12:00 [RFC i-iv] ASoC: Add support for cross-device paths without dai and without name collision Jarkko Nikula
2010-10-29 12:00 ` [RFC_i/iv 1/3] ASoC: Decouple DAPM from CODECs. Part core (will be squashed) Jarkko Nikula
2010-10-29 20:04 ` Mark Brown
2010-10-30 18:01 ` Liam Girdwood
2010-10-31 18:13 ` Jarkko Nikula
2010-11-01 13:13 ` Mark Brown
2010-11-04 12:38 ` [PATCH] ASoC: Decouple DAPM from CODECs Jarkko Nikula
2010-11-05 3:29 ` Mark Brown
2010-11-05 7:20 ` Jarkko Nikula
2010-11-05 13:38 ` Mark Brown
2010-11-05 13:53 ` Jarkko Nikula
2010-11-05 14:02 ` Mark Brown
[not found] ` <1288353618-21753-3-git-send-email-jhnikula@gmail.com>
2010-10-29 13:45 ` [RFC_i/iv 2/3] ASoC: Decouple DAPM from CODECs. Part codecs (will be squashed) Jarkko Nikula
2010-10-29 20:45 ` Mark Brown
[not found] ` <1288353618-21753-4-git-send-email-jhnikula@gmail.com>
2010-10-29 20:47 ` Mark Brown [this message]
2010-10-31 18:11 ` [RFC_i/iv 3/3] ASoC: Decouple DAPM from CODECs. Part platforms " Jarkko Nikula
2010-11-01 13:14 ` 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=20101029204725.GF3921@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=lrg@slimlogic.co.uk \
/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).