From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dong Aisheng <b29396@freescale.com>
Cc: alsa-devel@alsa-project.org, lrg@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/1] ASoC: soc-dapm: warn if no avaiable path found for widget kcontrol
Date: Sun, 29 Jul 2012 21:22:19 +0100 [thread overview]
Message-ID: <20120729202219.GA4384@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1343387941-25266-1-git-send-email-b29396@freescale.com>
On Fri, Jul 27, 2012 at 07:19:01PM +0800, Dong Aisheng wrote:
> From: Dong Aisheng <dong.aisheng@linaro.org>
>
> This could help people know what's wrong going on if the required
> path is not registered.
This isn't a good idea, it's fairly common for widgets to have a "None"
option which isn't expected to have an input.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/1] ASoC: soc-dapm: warn if no avaiable path found for widget kcontrol
Date: Sun, 29 Jul 2012 21:22:19 +0100 [thread overview]
Message-ID: <20120729202219.GA4384@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1343387941-25266-1-git-send-email-b29396@freescale.com>
On Fri, Jul 27, 2012 at 07:19:01PM +0800, Dong Aisheng wrote:
> From: Dong Aisheng <dong.aisheng@linaro.org>
>
> This could help people know what's wrong going on if the required
> path is not registered.
This isn't a good idea, it's fairly common for widgets to have a "None"
option which isn't expected to have an input.
next prev parent reply other threads:[~2012-07-29 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 11:19 [RFC PATCH 1/1] ASoC: soc-dapm: warn if no avaiable path found for widget kcontrol Dong Aisheng
2012-07-27 11:19 ` Dong Aisheng
2012-07-29 20:22 ` Mark Brown [this message]
2012-07-29 20:22 ` Mark Brown
2012-08-01 7:49 ` Dong Aisheng
2012-08-01 7:49 ` Dong Aisheng
2012-08-01 12:15 ` Mark Brown
2012-08-01 12:15 ` Mark Brown
2012-08-02 7:08 ` Dong Aisheng
2012-08-02 7:08 ` Dong Aisheng
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=20120729202219.GA4384@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=b29396@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@ti.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.