From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: soc-dapm: Include quotes around contents in debugfs entries
Date: Fri, 25 Feb 2011 11:52:24 +0000 [thread overview]
Message-ID: <20110225115224.GB28980@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1298567372-7030-1-git-send-email-dp@opensource.wolfsonmicro.com>
On Thu, Feb 24, 2011 at 05:09:32PM +0000, Dimitris Papastamos wrote:
> Sometimes the name of the control switch of a dapm route contains
> spaces which makes it impossible to distinguish it from the source widget.
> Add quotes around the names of the widgets to makes these parsable.
>
> Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Applied, thanks.
prev parent reply other threads:[~2011-02-25 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 17:09 [PATCH] ASoC: soc-dapm: Include quotes around contents in debugfs entries Dimitris Papastamos
2011-02-25 9:01 ` Liam Girdwood
2011-02-25 11:52 ` 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=20110225115224.GB28980@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=patches@opensource.wolfsonmicro.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 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.