From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, arnd@arndb.de, lrg@ti.com,
lee.jones@linaro.org, swarren@wwwdotorg.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/3] regulator: dt: add policy to match regulator with prop "regulator-compatible"
Date: Wed, 20 Jun 2012 11:00:58 +0100 [thread overview]
Message-ID: <20120620100058.GD3978@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdYSLiLZwVwY1tU9PWGTx2EGP6OykeXE5rtwRKAHror-Yg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Wed, Jun 20, 2012 at 10:59:32AM +0200, Linus Walleij wrote:
> If I had today deployed the device trees generated prior to this patch,
> and try to boot kernels after this patch with the same device tree,
> would they still work as expected?
> I don't know it it's an issue right now, but at some point we need to
> realize that people will expect old device trees to work on newer
> kernels.
I don't think anyone's taking that idea terribly seriously right now for
ARM, lots of the core SoC bindings are still in flux or not there.
Even for PowerPC where this has apparently been achieved I've still had
to push back on new mandatory properties being added :/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-20 10:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 14:28 [PATCH V2 0/3] regulator: dt: add policy to match regulator with prop "regulator-compatible" Laxman Dewangan
2012-06-19 14:28 ` [PATCH V2 1/3] regulator: dt: regulator match by regulator-compatible Laxman Dewangan
2012-06-19 17:39 ` Stephen Warren
2012-06-19 14:28 ` [PATCH V2 2/3] regulator: dt: add policy to have property "regulator-compatible" Laxman Dewangan
2012-06-19 17:43 ` Stephen Warren
2012-06-19 17:53 ` Mark Brown
2012-06-19 18:03 ` Stephen Warren
2012-06-19 18:06 ` Mark Brown
2012-06-19 14:28 ` [PATCH V2 3/3] ARM: dts: db8500: add node property "regulator-compatible" regulator node Laxman Dewangan
2012-06-19 16:13 ` Lee Jones
2012-06-19 17:32 ` Stephen Warren
2012-06-20 7:09 ` Lee Jones
2012-06-20 7:39 ` Laxman Dewangan
2012-06-20 8:01 ` Lee Jones
2012-06-20 8:19 ` Laxman Dewangan
2012-06-20 8:56 ` Lee Jones
2012-06-20 10:06 ` Mark Brown
2012-06-20 11:25 ` Lee Jones
2012-06-20 11:27 ` Laxman Dewangan
2012-06-20 11:37 ` Lee Jones
2012-06-20 16:14 ` Stephen Warren
2012-06-19 17:29 ` Stephen Warren
2012-06-20 8:59 ` [PATCH V2 0/3] regulator: dt: add policy to match regulator with prop "regulator-compatible" Linus Walleij
2012-06-20 10:00 ` Mark Brown [this message]
2012-06-20 16:23 ` Stephen Warren
2012-06-21 8:02 ` Linus Walleij
2012-06-21 9:53 ` Mark Brown
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=20120620100058.GD3978@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).