alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC_iv/iv 1/1] ASoC: Add optional name_prefix to struct snd_soc_dev_map
Date: Mon, 1 Nov 2010 13:51:44 -0400	[thread overview]
Message-ID: <20101101175144.GF24814@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20101031201243.3ef62461.jhnikula@gmail.com>

On Sun, Oct 31, 2010 at 08:12:43PM +0200, Jarkko Nikula wrote:

> associating a prefix with codec name. Compile tested diff below.

Oh, didn't spot this first time round due to sig sep - that diff looks a
lot better at first glance.  We need a way to get the data into the card
I guess.

      parent reply	other threads:[~2010-11-01 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 12:03 [RFC_iv/iv 1/1] ASoC: Add optional name_prefix to struct snd_soc_dev_map Jarkko Nikula
2010-10-29 21:42 ` Mark Brown
2010-10-31 18:12   ` Jarkko Nikula
2010-11-01 17:49     ` Mark Brown
2010-11-01 17:51     ` 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=20101101175144.GF24814@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jhnikula@gmail.com \
    --cc=lrg@slimlogic.co.uk \
    /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).