| 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: <1310352837-4277-4-git-send-email-broonie@opensource.wolfsonmicro.com> Date: Mon, 11 Jul 2011 11:53:55 +0900 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Jeremy Kerr <jeremy.kerr@...onical.com> Cc: Grant Likely <grant@...retlab.ca>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-sh@...r.kernel.org, patches@...nsource.wolfsonmicro.com, Mark Brown <broonie@...nsource.wolfsonmicro.com> Subject: [PATCH 4/6] clk: Add Kconfig option to build all generic clk drivers Currently drivers for the generic clk subsystem must be selected by platforms using them in order to enable build. When doing development on the API or generic build time testing it is useful to be able to build unused drivers in order to improve coverage so supply a Kconfig option which allows this. Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com> --- drivers/clk/Kconfig | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig index 75d2902..1fd0070 100644 --- a/drivers/clk/Kconfig +++ b/drivers/clk/Kconfig @@ -1,4 +1,3 @@ - config CLKDEV_LOOKUP bool select HAVE_CLK @@ -6,6 +5,16 @@ config CLKDEV_LOOKUP config GENERIC_CLK bool +config GENERIC_CLK_BUILD_TEST + bool "Build all generic clock drivers" + depends on EXPERIMENTAL && GENERIC_CLK + select GENERIC_CLK_FIXED + select GENERIC_CLK_GATE + help + Enable all possible generic clock drivers. This is only + useful for improving build coverage, it is not useful for + production kernel builds. + config GENERIC_CLK_FIXED bool depends on GENERIC_CLK -- 1.7.5.4 -- 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