All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH v2] ALSA: PCM - Add PCM creation API for internal PCMs.
Date: Thu, 09 Feb 2012 08:41:02 +0000	[thread overview]
Message-ID: <1328776862.3951.3.camel@odin> (raw)
In-Reply-To: <s5hhaz0jtw4.wl%tiwai@suse.de>

On Thu, 2012-02-09 at 09:25 +0100, Takashi Iwai wrote:
> At Wed, 8 Feb 2012 22:57:34 +0000,
> Mark Brown wrote:
> > 
> > [1  <text/plain; us-ascii (7bit)>]
> > On Wed, Feb 08, 2012 at 10:35:57PM +0100, Takashi Iwai wrote:
> > > At Wed,  8 Feb 2012 20:33:31 +0000,
> > > Liam Girdwood wrote:
> > 
> > > > The new ASoC dynamic PCM core needs to create PCMs and substreams that are
> > > > for use by internal ASoC drivers only and not visible to userspace for
> > > > direct IO. These new PCMs are similar to regular PCMs expect they have no
> > > > device nodes or procfs entries. The ASoC component drivers use them in exactly
> > > > the same way as regular PCMs for PCM and DAI operations.
> > 
> > > The changes look OK to me, but could you fix a few errors/warnings
> > > by checkpatch.pl?
> > 
> > Since Liam's got a whole raft of ASoC changes depending on this one can
> > you please either apply it to a branch or ack it for merge via ASoC?
> 
> OK, now I fixed coding-style issues by myself and applied the patch.
> It's found in an individual branch, topic/pcm-internal of sound git
> tree.  Feel free to pull this branch to your trees.
> 

Appologies, I didn't catch that after rebasing from V1.

Liam

  reply	other threads:[~2012-02-09  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 20:33 [PATCH v2] ALSA: PCM - Add PCM creation API for internal PCMs Liam Girdwood
2012-02-08 21:35 ` Takashi Iwai
2012-02-08 22:57   ` Mark Brown
2012-02-09  8:25     ` Takashi Iwai
2012-02-09  8:41       ` Liam Girdwood [this message]
2012-02-09 10:44       ` 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=1328776862.3951.3.camel@odin \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=tiwai@suse.de \
    /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.