| 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
| ||
|
Message-ID: <5457BD85.2070901@topic.nl> Date: Mon, 03 Nov 2014 18:38:13 +0100 From: Mike Looijmans <mike.looijmans@...ic.nl> To: Mark Brown <broonie@...nel.org> CC: lgirdwood@...il.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2] Add ltc3562 voltage regulator driver On 3-11-2014 16:10, Mark Brown wrote: > On Mon, Nov 03, 2014 at 03:48:56PM +0100, Mike Looijmans wrote: >> On 11/03/2014 01:09 PM, Mark Brown wrote: > >>> No function calls, just use regulators_node. What is unclear about the >>> functionality? > >> I don't understand what you mean by "regulators_node". > >> "grep -R regulators_node *" in the kernel source tree returns no results, >> nor does http://lxr.free-electrons.com/ident?i=regulators_node > > You need to develop against current versions of the kernel, this is > something that was merged into Linus' tree during the merge window. Is this an absolute show-stopper for you? With some effort I could move from our current 3.15 to 3.17, but even that wouldn't be recent enough then. I can justify spending a few days on getting the driver integrated into mainline, even if the initial version cost less than that; but moving everything to mainline is going to take weeks and the boss is definitely going to say "no" to that. -- Mike Looijmans -- 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