From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: [PATCH 0/3] introduce device_buffer
Date: Fri, 31 Aug 2012 14:22:03 -0700 [thread overview]
Message-ID: <20120831212202.GA5495@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1346353958-7746-1-git-send-email-vinod.koul@linux.intel.com>
On Fri, Aug 31, 2012 at 12:42:35AM +0530, Vinod Koul wrote:
> Old wine ina new bottle, so here is the second attempt for adding the notion of
> how devices (in my case a DSP) can buffer data and that can be used by sound
> core
This all looks good for me.
prev parent reply other threads:[~2012-08-31 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 19:12 [PATCH 0/3] introduce device_buffer Vinod Koul
2012-08-30 19:12 ` [PATCH 1/3] ALSA: pcm - " Vinod Koul
2012-08-30 19:12 ` [PATCH 2/3] ASoC: add device_buffer in asoc Vinod Koul
2012-08-30 19:12 ` [PATCH 3/3] ASoC: mid-x86 - implement buffer query in sst_platform driver Vinod Koul
2012-08-31 21:22 ` Mark Brown [this message]
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=20120831212202.GA5495@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@linux.intel.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;
as well as URLs for NNTP newsgroup(s).