Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 0/3] alsa-lib: Improve 2.1 surround support
Date: Fri, 28 Feb 2014 09:15:15 +0100	[thread overview]
Message-ID: <s5hvbvzlkks.wl%tiwai@suse.de> (raw)
In-Reply-To: <1393574227-25732-1-git-send-email-david.henningsson@canonical.com>

At Fri, 28 Feb 2014 08:57:04 +0100,
David Henningsson wrote:
> 
> Thanks Takashi for your encouraging review,
> 
> Diff since last version is only the things you remarked about in the first
> patch series.
> 
>  > Besides that, I find it also OK to just return the channel (>= 0) or a
>  > negative error.  But it's no big matter in which form is.
> 
> This one I didn't change, just because then I would just have had to change it
> back in the second patch anyway.

OK, applied all patches now.
Thanks!


Takashi

> 
> David Henningsson (3):
>   route: Allow chmap syntax for slave channels in ttable
>   route: Select slave chmap based on ttable information
>   conf: Allow 2.1 surround to use different number of channels
> 
>  src/conf/pcm/surround21.conf |    7 +-
>  src/pcm/pcm_route.c          |  323 +++++++++++++++++++++++++++++++++++++-----
>  2 files changed, 290 insertions(+), 40 deletions(-)
> 
> -- 
> 1.7.9.5
> 

      parent reply	other threads:[~2014-02-28  8:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28  7:57 [PATCH v2 0/3] alsa-lib: Improve 2.1 surround support David Henningsson
2014-02-28  7:57 ` [PATCH v2 1/3] route: Allow chmap syntax for slave channels in ttable David Henningsson
2014-02-28  7:57 ` [PATCH v2 2/3] route: Select slave chmap based on ttable information David Henningsson
2014-02-28 13:49   ` Raymond Yau
2014-02-28 13:52     ` David Henningsson
2014-02-28  7:57 ` [PATCH v2 3/3] conf: Allow 2.1 surround to use different number of channels David Henningsson
2014-02-28  8:15 ` Takashi Iwai [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=s5hvbvzlkks.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.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