From: Shawn Guo <shawn.guo@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] regulator: core: Use postcore_initcall(regulator_init_complete)
Date: Mon, 16 Dec 2013 16:40:52 +0800 [thread overview]
Message-ID: <20131216084050.GA30671@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <CAOMZO5DHYgJY4dpB+znx9g3TChUNn3ujdtCf0OsmkbGtrE9R1A@mail.gmail.com>
On Sun, Dec 15, 2013 at 03:03:00PM -0200, Fabio Estevam wrote:
> On Sun, Dec 15, 2013 at 11:06 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
>
> > What is going on about that patch?
>
> Mark fixed the problem with the following commits:
Thanks for the info, Fabio.
Shawn
>
> commit 75bc9641cadd2a3f91f9c2e7f2fdfdeb8bd4b1d6
> Author: Mark Brown <broonie@linaro.org>
> Date: Wed Nov 27 16:22:53 2013 +0000
>
> regulator: core: Check for DT every time we check full constraints
>
> Eliminate the gap between DT becoming available and this being used to say
> we have full constraints by checking directly for DT every time we check
> for full constraints. This improves interoperaton with optional regulator
> support.
>
> Signed-off-by: Mark Brown <broonie@linaro.org>
> Tested-by: Fabio Estevam <fabio.estevam@freescale.com>
>
> commit 87b2841753e1694fc96fefb467f6aff9940b07af
> Author: Mark Brown <broonie@linaro.org>
> Date: Wed Nov 27 16:13:10 2013 +0000
>
> regulator: core: Replace checks of have_full_constraints with a function
>
> Simple code reorganisation so we can change the logic for deciding what
> full constraints are more easily.
>
> Signed-off-by: Mark Brown <broonie@linaro.org>
>
> Regards,
>
> Fabio Estevam
prev parent reply other threads:[~2013-12-16 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 21:57 Fabio Estevam
2013-11-26 0:46 ` Mark Brown
2013-11-27 0:55 ` Mark Brown
2013-12-15 13:06 ` Shawn Guo
2013-12-15 17:03 ` Fabio Estevam
2013-12-16 8:40 ` Shawn Guo [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=20131216084050.GA30671@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®