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: <CACRpkdYSLiLZwVwY1tU9PWGTx2EGP6OykeXE5rtwRKAHror-Yg@mail.gmail.com>
Date:	Wed, 20 Jun 2012 10:59:32 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Laxman Dewangan <ldewangan@...dia.com>,
	devicetree-discuss@...ts.ozlabs.org
Cc:	broonie@...nsource.wolfsonmicro.com, 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 Tue, Jun 19, 2012 at 4:28 PM, Laxman Dewangan <ldewangan@...dia.com> wrote:

> add policy to match regulator with the property of "regulator-compatible" of each
> child regulator node with their hardware counterparts name.
> Modify documentation as well to reflect this change and dts files.
>
> Changes from V1:
> - Modify the existing of_regulator_match() to use the property
>  "regulator-compatible" of each child node of regulator for
>   matching rather than child node name.
> - Documentation change to reflect this policy who are using the
>  of_regulator_match().
> - Modify the dts file to absorb this policy.

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.

Yours,
Linus Walleij
--
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/