public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] ARM: pxa: add regulator_has_full_constraints to corgi board file
Date: Thu, 04 Dec 2014 22:20:55 +0100	[thread overview]
Message-ID: <874mtbyuvc.fsf@free.fr> (raw)
In-Reply-To: <20141204204939.GY7712@sirena.org.uk> (Mark Brown's message of "Thu, 4 Dec 2014 20:49:39 +0000")

Mark Brown <broonie@kernel•org> writes:

> On Thu, Dec 04, 2014 at 09:41:45PM +0100, Robert Jarzmik wrote:
>> Dmitry Eremin-Solenikov <dbaryshkov@gmail•com> writes:
>
>> > +	regulator_has_full_constraints();
>
>> Added Mark for review, as I was thinking regulator_has_full_constraints() was to
>> be used to disable unused regulators, a bit like in the clock framework, rather
>> than provide a way to provide automatically dummy regulators.
>
>> If Mark acks, I'll take the serie.
>
> It's both, it's telling the core that the board has told it about all
> the regulator mappings it's ever going to tell it about.
OK, I'll take that as an Acked-by then.

Cheers.

-- 
Robert

  reply	other threads:[~2014-12-04 21:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 11:10 [PATCH 1/3] ARM: pxa: add regulator_has_full_constraints to corgi board file Dmitry Eremin-Solenikov
2014-12-04 11:10 ` [PATCH 2/3] ARM: pxa: add regulator_has_full_constraints to poodle " Dmitry Eremin-Solenikov
2014-12-04 11:10 ` [PATCH 3/3] ARM: pxa: add regulator_has_full_constraints to spitz " Dmitry Eremin-Solenikov
2014-12-04 20:41 ` [PATCH 1/3] ARM: pxa: add regulator_has_full_constraints to corgi " Robert Jarzmik
2014-12-04 20:49   ` Mark Brown
2014-12-04 21:20     ` Robert Jarzmik [this message]
2014-12-07 16:03       ` Robert Jarzmik

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=874mtbyuvc.fsf@free.fr \
    --to=robert.jarzmik@free$(echo .)fr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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