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: Mon, 07 Nov 2011 11:57:27 +0530 From: Rajendra Nayak <rnayak@...com> To: Olof Johansson <olof@...om.net> CC: Mark Brown <broonie@...nsource.wolfsonmicro.com>, grant.likely@...retlab.ca, patches@...aro.org, tony@...mide.com, devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org, lrg@...com, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH v4 1/4] regulator: helper routine to extract regulator_init_data On Saturday 05 November 2011 03:46 AM, Olof Johansson wrote: >>> Yeah, ok, but it shouldn't be part of the description of regulator >>> >> properties per se. See how gpio does it, defining how a gpio-specifier >>> >> is crafted. The equivalent should be done for regulators. >> > >> > That seems to be pretty much exactly what's being done here, and like >> > the GPIO bindings it's specified in the core document. Though perhaps >> > there's some aspect of how the document is written that's missing. > > Yep, sounds good. A slightly more elaborate description of the binding > inspired by the gpio.txt document would be the way to do that. > Ok, will add more elaborate documentation for this in the core bindings. -- 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