From: Jarkko Nikula <jhnikula@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Eduardo Valentin <eduardo.valentin@nokia.com>,
Takashi Iwai <tiwai@suse.de>,
Linux-OMAP <linux-omap@vger.kernel.org>,
ALSA-Devel <alsa-devel@vger.kernel.org>,
"Nurkkala Eero.An (EXT-Offcode/Oulu)"
<ext-Eero.Nurkkala@nokia.com>,
"Ujfalusi Peter (Nokia-D/Tampere)" <peter.ujfalusi@nokia.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCHv5 00/20] OMAP ASoC changes in DMA utilization
Date: Thu, 20 Aug 2009 19:15:42 +0300 [thread overview]
Message-ID: <20090820191542.bc7b0d4d.jhnikula@gmail.com> (raw)
In-Reply-To: <20090820143017.GH12309@atomide.com>
On Thu, 20 Aug 2009 17:30:18 +0300
Tony Lindgren <tony@atomide.com> wrote:
> * Eduardo Valentin <eduardo.valentin@nokia.com> [090820 16:36]:
> > Hello guys,
> >
> > I've updated this series after some previous confusion from my side.
> >
> > Now that all dependencies are merged (Janusz's patches and Jarkko's patch),
> > I've based this series on Takashi's tree (master branch).
> >
Mark: Set applies and works (with Beagle) on top of both master and
topic/asoc branches.
> > I've also talked with Tony and he agrees to have this changes merged
> > by alsa tree. And as pointed by Jarkko, the mcbsp code is currently
> > used only by Audio inside OMAP code. So, that should be safe.
>
> You might want to merge patches 5 and 6 together as 5 adds the
> fifo, then 6 limits it's size. But in general, for patches
> 1 - 14: Acked-by: Tony Lindgren <tony@atomide.com>
>
15-20: Acked-by: Jarkko Nikula <jhnikula@gmail.com>
--
Jarkko
next prev parent reply other threads:[~2009-08-20 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 13:22 [PATCHv5 00/20] OMAP ASoC changes in DMA utilization Eduardo Valentin
2009-08-20 14:30 ` Tony Lindgren
2009-08-20 15:56 ` Eduardo Valentin
2009-08-20 16:15 ` Jarkko Nikula [this message]
2009-08-20 19:17 ` 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=20090820191542.bc7b0d4d.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@vger.kernel.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eduardo.valentin@nokia.com \
--cc=ext-Eero.Nurkkala@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--cc=tiwai@suse.de \
--cc=tony@atomide.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