From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Mack <daniel@caiaq.de>
Cc: Sven Neumann <s.neumann@raumfeld.com>,
alsa-devel@alsa-project.org,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Michael Hirsch <m.hirsch@raumfeld.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ALSA: ASoC: move dma_data from snd_soc_dai to snd_soc_pcm_stream
Date: Sat, 20 Mar 2010 15:30:22 +0000 [thread overview]
Message-ID: <20100320153022.GA32428@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20100320145428.GC30801@buzzloop.caiaq.de>
On Sat, Mar 20, 2010 at 03:54:29PM +0100, Daniel Mack wrote:
> Agreed. However, I believe when pushed to .34, it will get greater
> exposion, and regressions would more likely be found and get fixed.
> Faster than in your for-2.6.35 branch I mean.
I want it to at least appear in -next for a few days before backporting.
That will get a moderate amount of automatic cover, and would make me
much more happy about pushing a version for .34. If you want to do the
backport to .34 that'd be helpful.
next prev parent reply other threads:[~2010-03-20 15:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 16:17 Memory corruption in ASoC Daniel Mack
2010-03-18 16:43 ` Mark Brown
2010-03-18 16:48 ` Daniel Mack
2010-03-18 17:07 ` Mark Brown
2010-03-18 17:35 ` Liam Girdwood
2010-03-18 18:08 ` [PATCH] ALSA: ASoC: move dma_data from snd_soc_dai to snd_soc_pcm_stream Daniel Mack
2010-03-18 18:11 ` Daniel Mack
2010-03-18 18:22 ` Mark Brown
2010-03-18 18:28 ` Daniel Mack
2010-03-18 19:23 ` Daniel Mack
2010-03-19 6:56 ` Peter Ujfalusi
2010-03-19 7:08 ` Daniel Mack
2010-03-19 15:14 ` Mark Brown
2010-03-19 18:39 ` Daniel Mack
2010-03-19 19:54 ` Mark Brown
2010-03-20 14:54 ` Daniel Mack
2010-03-20 15:30 ` Mark Brown [this message]
2010-03-20 15:39 ` Daniel Mack
2010-03-20 16:14 ` Mark Brown
2010-03-22 9:10 ` Daniel Mack
2010-03-22 9:11 ` Daniel Mack
2010-04-01 17:18 ` Daniel Mack
2010-03-20 15:43 ` Daniel Mack
2010-03-19 9:14 ` Jarkko Nikula
2010-03-19 8:50 ` Liam Girdwood
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=20100320153022.GA32428@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@caiaq.de \
--cc=lrg@slimlogic.co.uk \
--cc=m.hirsch@raumfeld.com \
--cc=peter.ujfalusi@nokia.com \
--cc=s.neumann@raumfeld.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.