[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DHYgJY4dpB+znx9g3TChUNn3ujdtCf0OsmkbGtrE9R1A@mail.gmail.com>
Date: Sun, 15 Dec 2013 15:03:00 -0200
From: Fabio Estevam <festevam@...il.com>
To: Shawn Guo <shawn.guo@...aro.org>
Cc: Mark Brown <broonie@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Thierry Reding <thierry.reding@...il.com>,
Fabio Estevam <fabio.estevam@...escale.com>
Subject: Re: [PATCH] regulator: core: Use postcore_initcall(regulator_init_complete)
On Sun, Dec 15, 2013 at 11:06 AM, Shawn Guo <shawn.guo@...aro.org> wrote:
> What is going on about that patch?
Mark fixed the problem with the following commits:
commit 75bc9641cadd2a3f91f9c2e7f2fdfdeb8bd4b1d6
Author: Mark Brown <broonie@...aro.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@...aro.org>
Tested-by: Fabio Estevam <fabio.estevam@...escale.com>
commit 87b2841753e1694fc96fefb467f6aff9940b07af
Author: Mark Brown <broonie@...aro.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@...aro.org>
Regards,
Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists