From: Juha Keski-Saari <ext-juha.1.keski-saari@nokia.com>
To: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"dbrownell@users.sourceforge.net"
<dbrownell@users.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"De-Schrijver Peter (Nokia-D/Helsinki)"
<Peter.De-Schrijver@nokia.com>,
"Valentin Eduardo (Nokia-D/Helsinki)"
<eduardo.valentin@nokia.com>
Subject: Re: [PATCHv2 3/3] Define critical regulators as always_on
Date: Wed, 25 Nov 2009 13:36:39 +0200 [thread overview]
Message-ID: <1259148999.10122.25.camel@keskisaa-workstation> (raw)
In-Reply-To: <20091125111336.GF17420@opensource.wolfsonmicro.com>
On Wed, 2009-11-25 at 12:13 +0100, ext Mark Brown wrote:
> On Wed, Nov 25, 2009 at 12:29:59PM +0200, Juha Keski-Saari wrote:
>
> > + case TWL4030_REG_VINTDIG:
> > + c->always_on = true;
> > + break;
>
> One other thing I noticed having seen the MFD series - is this going to
> build without the separate MFD patch you've posted?
Yes, the changes to twl4030-regulator.c compile without the changes the
MFD patch set makes to twl4030-core.c and twl4030.h
prev parent reply other threads:[~2009-11-25 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 10:04 [PATCHv2 0/3] for-next: Add all twl4030 regulators to RegFW Juha Keski-Saari
2009-11-25 10:04 ` [PATCHv2 1/3] twl4030-regulator: Add all TWL regulators to twreg_info Juha Keski-Saari
2009-11-25 13:38 ` Juha Keski-Saari
2009-11-25 13:49 ` Liam Girdwood
2009-11-25 14:22 ` Juha Keski-Saari
2009-11-25 14:33 ` Mark Brown
2009-11-25 18:19 ` Liam Girdwood
2009-11-25 10:04 ` [PATCHv2 2/3] Reset REMAP configuration in regulator probe Juha Keski-Saari
2009-11-25 10:04 ` [PATCHv2 3/3] Define critical regulators as always_on Juha Keski-Saari
2009-11-25 10:14 ` Mark Brown
2009-11-25 10:29 ` Juha Keski-Saari
2009-11-25 11:13 ` Mark Brown
2009-11-25 11:36 ` Juha Keski-Saari [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=1259148999.10122.25.camel@keskisaa-workstation \
--to=ext-juha.1.keski-saari@nokia.com \
--cc=Peter.De-Schrijver@nokia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dbrownell@users.sourceforge.net \
--cc=eduardo.valentin@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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
all inboxes | Powered by JetHome®