From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lu Guanqun <guanqun.lu@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Improve error reporting in Speyside WM8962 driver
Date: Thu, 30 Jun 2011 11:02:28 -0700 [thread overview]
Message-ID: <20110630180225.GB5064@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110630165617.GF26397@qtel.sh.intel.com>
On Fri, Jul 01, 2011 at 12:56:17AM +0800, Lu Guanqun wrote:
> On Thu, Jun 30, 2011 at 05:18:51AM +0800, Mark Brown wrote:
> > if (ret < 0)
> > - pr_err("Failed to start FLL\n");
> > + pr_err("Failed to start FLL: %d\n");
> missed 'ret' here? :)
Fixed locally, Liam I'll not bother reposting if you're otherwise OK?
next prev parent reply other threads:[~2011-06-30 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 21:18 [PATCH] ASoC: Improve error reporting in Speyside WM8962 driver Mark Brown
2011-06-30 16:56 ` Lu Guanqun
2011-06-30 18:02 ` Mark Brown [this message]
2011-06-30 18:02 ` Lu Guanqun
2011-06-30 18:08 ` Liam Girdwood
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=20110630180225.GB5064@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=guanqun.lu@intel.com \
--cc=lrg@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox