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, 24 Oct 2011 11:19:25 +0200 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Rajendra Nayak <rnayak@...com> Cc: Grant Likely <grant.likely@...retlab.ca>, Shawn Guo <shawn.guo@...escale.com>, 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 v2 3/5] regulator: helper routine to extract regulator_init_data On Mon, Oct 24, 2011 at 02:23:50PM +0530, Rajendra Nayak wrote: > How about the driver passing the of_node to be associated with the > regulator, as part of regulator_desc, to the regulator core, > instead of this complete DT search and the restriction of having > to match DT node names with names in regulator_desc. regulator_desc should be const so that we handle multiple instances of the same device nicely. We could pass the information in as an argument I guess. -- 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