From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: Axel Lin <axel.lin@ingics.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] regulator: core: support shared enable GPIO concept
Date: Fri, 1 Mar 2013 15:17:58 +0800 [thread overview]
Message-ID: <20130301071747.GG25302@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998F792729F1@DQHE02.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
On Mon, Feb 18, 2013 at 06:50:39AM +0000, Kim, Milo wrote:
> + pin->gpio = config->ena_gpio;
> + pin->ena_gpio_invert = config->ena_gpio_invert;
> + list_add(&pin->list, ®ulator_ena_gpio_list);
We should really validate that the invert settings are consistent but
it's not so important since this is a user error that they'd probably
notice.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-03-01 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 6:50 [PATCH v3 1/4] regulator: core: support shared enable GPIO concept Kim, Milo
2013-02-19 1:58 ` Axel Lin
2013-03-01 7:17 ` Mark Brown [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=20130301071747.GG25302@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Milo.Kim@ti.com \
--cc=axel.lin@ingics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox