linux-kernel - Re: [PATCH v2 1/7] clk: Add a generic clock infrastructure

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20111027115411.GA4713@glitch>
Date:	Thu, 27 Oct 2011 13:54:11 +0200
From:	Domenico Andreoli <cavokz@...il.com>
To:	Mike Turquette <mturquette@...com>
Cc:	jeremy.kerr@...onical.com, paul@...an.com,
	linaro-dev@...ts.linaro.org, linus.walleij@...ricsson.com,
	patches@...aro.org, broonie@...nsource.wolfsonmicro.com,
	magnus.damm@...il.com, linux-kernel@...r.kernel.org,
	eric.miao@...aro.org, grant.likely@...retlab.ca,
	dsaxena@...aro.org, tglx@...utronix.de, amit.kucheria@...aro.org,
	skannan@...cinc.com, linux@....linux.org.uk,
	arnd.bergmann@...aro.org, sboyd@...inc.com,
	richard.zhao@...aro.org, shawn.guo@...escale.com,
	linux-arm-kernel@...ts.infradead.org,
	Rob Herring <robherring2@...il.com>
Subject: Re: [PATCH v2 1/7] clk: Add a generic clock infrastructure

Hi,

On 09/22/2011 05:26 PM, Mike Turquette wrote:
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 3530927..c53ed59 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -5,3 +5,6 @@ config CLKDEV_LOOKUP
>  
>  config HAVE_MACH_CLKDEV
>  	bool
> +
> +config GENERIC_CLK
> +	bool

Now that Russel's prepare/unprepare patch is mainlined, I think you
want to select HAVE_CLK_PREPARE here (and remove your prepare/unprepare
function declarations in clk.h).

Regards,
Domenico
--
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/