From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] regulator: Report error codes for bulk operations
Date: Sun, 18 Oct 2009 14:54:10 +0100 [thread overview]
Message-ID: <1255874050.8480.55.camel@odin> (raw)
In-Reply-To: <1255435610-9765-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tue, 2009-10-13 at 13:06 +0100, Mark Brown wrote:
> If we're going to log an error we may as well log what the error
> code that we're failing on is.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Both Applied.
Thanks
Liam
prev parent reply other threads:[~2009-10-18 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 12:06 [PATCH 1/2] regulator: Report error codes for bulk operations Mark Brown
2009-10-13 12:06 ` [PATCH 2/2] regulator: Handle missing constraints in _regulator_disable() Mark Brown
2009-10-18 13:54 ` Liam Girdwood [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=1255874050.8480.55.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.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 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.