Messages in this thread | | | Date | Wed, 20 Jun 2012 10:59:32 +0200 | Subject | Re: [PATCH V2 0/3] regulator: dt: add policy to match regulator with prop "regulator-compatible" | From | Linus Walleij <> |
| |
On Tue, Jun 19, 2012 at 4:28 PM, Laxman Dewangan <ldewangan@nvidia.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |