From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Krystian Garbaciak <krystian.garbaciak@diasemi.com>
Cc: Liam Girdwood <lrg@ti.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Fix bug in regulator_mode_to_status() core function.
Date: Wed, 11 Jul 2012 14:28:41 +0100 [thread overview]
Message-ID: <20120711132655.GG3938@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201207111221.q6BCLW8L014872@sw-eng-lt-dc-vm2>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
On Wed, Jul 11, 2012 at 01:10:01PM +0100, Krystian Garbaciak wrote:
> Fix typo for case REGULATOR_STATUS_STANDBY -> REGULATOR_MODE_STANDBY.
> For undefined mode, return REGULATOR_STATUS_ERROR (0 is not valid status).
This is deliberate. It's not reporting an error, it's reporting an
indeterminate status which is a different thing.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-11 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 12:10 [PATCH] regulator: Fix bug in regulator_mode_to_status() core function Krystian Garbaciak
2012-07-11 13:28 ` Mark Brown [this message]
2012-07-11 14:18 ` Krystian Garbaciak
2012-07-11 14:26 ` Mark Brown
2012-07-11 15:13 ` Krystian Garbaciak
2012-07-11 17:42 ` Mark Brown
2012-07-12 10:50 ` [PATCH] regulator: Fix a typo " Krystian Garbaciak
2012-07-12 12:53 ` [PATCH] regulator: Add REGULATOR_STATUS_UNDEFINED Krystian Garbaciak
2012-07-12 17:20 ` Mark Brown
2012-07-12 17:18 ` [PATCH] regulator: Fix a typo in regulator_mode_to_status() core function Mark Brown
2012-07-12 17:20 ` Mark Brown
[not found] <201208241500@sw-eng-lt-dc-vm2>
[not found] ` <201208241505@sw-eng-lt-dc-vm2>
2012-08-24 18:45 ` [RFC PATCH 4/8] hwmon: Add DA906x hardware monitoring support Guenter Roeck
2012-08-29 13:25 ` [PATCH] regulator: Fix bug in regulator_mode_to_status() core function Krystian Garbaciak
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=20120711132655.GG3938@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=krystian.garbaciak@diasemi.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox