| 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, 05 Apr 2012 00:40:01 +0530 From: Trilok Soni <tsoni@...eaurora.org> To: jean.pihet@...oldbits.com CC: linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, Kevin Hilman <khilman@...com>, "Rafael J. Wysocki" <rjw@...k.pl>, LKML <linux-kernel@...r.kernel.org>, Jean Pihet <j-pihet@...com> Subject: Re: [PATCH 2/9] ARM: OMAP2+: SmartReflex: move the driver specific macros in include/linux/power Hi Jean, On 3/19/2012 9:42 PM, jean.pihet@...oldbits.com wrote: > From: Jean Pihet<j-pihet@...com> > > Move the driver specific macros from the smartreflex header file > (arch/arm/mach-omap2/smartreflex.h) in a new header file > include/linux/power/smartreflex.h. > > This change makes the SmartReflex implementation ready for the move > to drivers/. I wonder why someone would need a new directory under drivers/power where the code is not about introducing new and generic AVS framework but it is all about OMAP specific code. What if tomorrow new generic AVS framework comes from different chip vendor? I am sure this kind of technology would be common in newer embedded chips. ---Trilok Soni -- -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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