| 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
| ||
|
Date: Thu, 21 Jun 2012 10:02:26 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Stephen Warren <swarren@...dotorg.org>, grant.likely@...retlab.ca Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>, Laxman Dewangan <ldewangan@...dia.com>, devicetree-discuss@...ts.ozlabs.org, rob.herring@...xeda.com, arnd@...db.de, lrg@...com, lee.jones@...aro.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 6:23 PM, Stephen Warren <swarren@...dotorg.org> wrote: > Related to this, I wonder if we need some scheme to tag individual > bindings as under-development vs. final, and some way to promote > bindings between those states (a bindings review board?!). Hm, we just have Documentation/devicetree/bindings and that's it. But compare to the Documentation/ABI: $ ls obsolete README removed stable testing I think we might want to mirror this structure for the bindings, putting all current bindings into testing. That said, this scheme has not always been very strictly enforced on sysfs etc. But the ambition is there. 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/
Powered by blists - more mailing lists