From: NeilBrown <neilb@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: check for devicetree early.
Date: Fri, 1 Nov 2013 20:15:40 +1100 [thread overview]
Message-ID: <20131101201540.3686ca90@notabene.brown> (raw)
In-Reply-To: <20131101064240.GN2493@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
On Thu, 31 Oct 2013 23:42:40 -0700 Mark Brown <broonie@kernel.org> wrote:
> On Fri, Nov 01, 2013 at 01:48:33PM +1100, NeilBrown wrote:
>
> > The behaviour of regulator core with respect to device-tree and
> > CONFIG_REGULATOR_DUMMY is inconsistent.
>
> Wei Ni reported this issue and is working on a patch which I'm expecting
> to do this as part of device tree initialisation rather than by faffing
> around with initcall ordering; this will be simpler and more robust
> since there won't be any possibility of races being introduced.
OK, thanks. Sounds like a better approach.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-11-01 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 2:48 [PATCH] regulator: check for devicetree early NeilBrown
2013-11-01 6:42 ` Mark Brown
2013-11-01 9:15 ` NeilBrown [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=20131101201540.3686ca90@notabene.brown \
--to=neilb@suse.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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