linux-kernel - Re: [PATCH V2 0/3] regulator: dt: add policy to match regulator with prop "regulator-compatible"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120620100058.GD3978@opensource.wolfsonmicro.com>
Date:	Wed, 20 Jun 2012 11:00:58 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Laxman Dewangan <ldewangan@...dia.com>,
	devicetree-discuss@...ts.ozlabs.org, grant.likely@...retlab.ca,
	rob.herring@...xeda.com, arnd@...db.de, lrg@...com,
	lee.jones@...aro.org, swarren@...dotorg.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 0/3] regulator: dt: add policy to match regulator with
 prop "regulator-compatible"

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 :/

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)