From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: soc-dapm: Fix breakage with incorrect codec pointer
Date: Sat, 18 Jun 2011 15:41:02 +0100 [thread overview]
Message-ID: <20110618144102.GB15674@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110618141046.GA4065@opensource.wolfsonmicro.com>
On Sat, Jun 18, 2011 at 03:10:46PM +0100, Dimitris Papastamos wrote:
> Yes that's true. That was a quick fix to temporarily take care of this
> problem.
With something like this I think it's probably as well to just revert
the original commit until we've got things sorted out, having the
feature sort of implemented but totally unusuble is probably worse than
not having it at all.
next prev parent reply other threads:[~2011-06-18 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 14:52 [PATCH] ASoC: soc-dapm: Fix breakage with incorrect codec pointer Dimitris Papastamos
2011-06-17 15:50 ` Liam Girdwood
2011-06-17 16:01 ` Mark Brown
2011-06-18 14:10 ` Dimitris Papastamos
2011-06-18 14:41 ` Mark Brown [this message]
2011-06-19 17:01 ` Dimitris Papastamos
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=20110618144102.GB15674@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.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