linux-kernel - Re: [PATCH] clk: Make the managed clk functions generically available

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 9 Sep 2012 21:57:03 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Lars-Peter Clausen <lars@...afoo.de>
Cc:	Mike Turquette <mturquette@...com>,
	Greg Ungerer <gerg@...inux.org>,
	Mark Brown <broonie@...ena.org.uk>,
	Julia Lawall <julia.lawall@...6.fr>,
	Artem Bityutskiy <dedekind1@...il.com>,
	linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] clk: Make the managed clk functions generically
	available

On Sun, Sep 09, 2012 at 05:01:02PM +0200, Lars-Peter Clausen wrote:
> The managed clk functions are currently only available when the generic clk
> lookup framework is build. But the managed clk functions are merely wrappers
> around clk_get and clk_put and do not depend on any specifics of the generic
> lookup functions and there are still quite a few custom implementations of the
> clk API. So make the managed functions available whenever the clk API is
> implemented.
> 
> The patch also removes the custom implementation of devm_clk_get for the
> coldfire platform.
> 
> Signed-off-by: Lars-Peter Clausen <lars@...afoo.de>

Definitely-Acked-by: Russell King <rmk+kernel@....linux.org.uk>

Thanks for finally cooking up a patch for this.
--
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/