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: [PATCHv2.1] ASoC: Add optional name_prefix for codec kcontrol, widget and route names
Date: Mon, 15 Nov 2010 15:24:18 +0000 [thread overview]
Message-ID: <20101115152417.GF12986@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1289673644-2493-1-git-send-email-jhnikula@gmail.com>
On Sat, Nov 13, 2010 at 08:40:44PM +0200, Jarkko Nikula wrote:
> There is a need to prefix codec kcontrol, widget and internal route names in
> an ASoC machine that has multiple codecs with conflicting names. The name
> collision would occur when codec drivers try to registering kcontrols with
> the same name or when building audio paths.
Applied, thanks.
prev parent reply other threads:[~2010-11-15 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 12:38 [PATCHv2] ASoC: Add optional name_prefix for codec kcontrol, widget and route names Jarkko Nikula
2010-11-13 18:40 ` [PATCHv2.1] " Jarkko Nikula
2010-11-15 15:24 ` 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=20101115152417.GF12986@rakim.wolfsonmicro.main \
--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).