From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ASoC: dapm: If one widget fails, do not force all subsequent widgets to fail too
Date: Tue, 31 Jul 2012 16:15:59 +0100 [thread overview]
Message-ID: <20120731151559.GB4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5017F514.4030106@linaro.org>
On Tue, Jul 31, 2012 at 04:09:08PM +0100, Lee Jones wrote:
> On 31/07/12 15:56, Mark Brown wrote:
> >To reiterate, this is in *no* way urgent or even a bug fix.
> It fixes sound in our driver.
> Without this the card failes to instantiate.
You're kidding, right? Fix the actual error.
> Isn't the return code incorrect? There are a multitude of reasons
> why snd_soc_dapm_new_control() would fail. No-memory is just one of
> them, so why do we force this probable lie?
I don't think anyone actually cares what the error code is, feel free to
pick another random number.
next prev parent reply other threads:[~2012-07-31 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 14:45 [PATCH 0/6] Bugfixes and clean-ups bound for the v3.6 RCs Lee Jones
2012-07-31 14:45 ` [PATCH 1/5] ASoC: dapm: If one widget fails, do not force all subsequent widgets to fail too Lee Jones
2012-07-31 14:56 ` Mark Brown
2012-07-31 15:09 ` Lee Jones
2012-07-31 15:15 ` Mark Brown [this message]
2012-07-31 14:45 ` [PATCH 2/5] ASoC: ab8500: Inform SoC Core that we have our own I/O arrangements Lee Jones
2012-07-31 15:38 ` Mark Brown
2012-07-31 14:45 ` [PATCH 3/5] ARM: ux500: Remove unused snowball_of_platform_devs struct Lee Jones
2012-07-31 14:45 ` [PATCH 4/5] ARM: ux500: Fix merge error, so such struct 'snd_soc_u8500' Lee Jones
2012-07-31 14:45 ` [PATCH 5/5] ARM: ux500: Ensure probing of Audio devices when Device Tree is enabled Lee Jones
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=20120731151559.GB4468@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).