From: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org"
<swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: About [PATCH 1/2] regulator: core: Provide a dummy regulator with full constraints
Date: Thu, 17 Oct 2013 18:39:56 +0800 [thread overview]
Message-ID: <525FBE7C.9080402@nvidia.com> (raw)
In-Reply-To: <20131017093701.GH2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 10/17/2013 05:37 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Oct 17, 2013 at 12:39:55PM +0800, Wei Ni wrote:
>
>> So do you mean it should call the regulator_has_full_constraints() in
>> the .init_machine for all machines? If so, this will affect all boards,
>> for example, in arch/arm/mach-tegra, if we set full constraints in the
>> shared board file tegra.c, all tegra boards will be set, is it right?
>
> Yes, but this is currently the case anyway for every system using DT -
> all we'd be doing is moving this call earlier in init.
Ok, I will send out patches for Tegra series.
>
> * Unknown Key
> * 0x7EA229BD
>
prev parent reply other threads:[~2013-10-17 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5253A17E.10503@nvidia.com>
[not found] ` <20131008090910.GW21581@sirena.org.uk>
[not found] ` <5253D489.7010900@nvidia.com>
[not found] ` <20131012121412.GJ2443@sirena.org.uk>
[not found] ` <525E17DE.6080301@nvidia.com>
[not found] ` <20131016103942.GG2443@sirena.org.uk>
[not found] ` <20131016103942.GG2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-17 4:39 ` About [PATCH 1/2] regulator: core: Provide a dummy regulator with full constraints Wei Ni
[not found] ` <525F6A1B.70505-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-17 9:37 ` Mark Brown
[not found] ` <20131017093701.GH2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-17 10:39 ` Wei Ni [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=525FBE7C.9080402@nvidia.com \
--to=wni-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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