linux-kernel - Re: [RFC] Common clock framework for external clock generators

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 13 May 2012 17:43:05 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Sebastian Hesselbarh <sebastian.hesselbarth@...glemail.com>
Cc:	linux-kernel@...r.kernel.org, mturquette@...com
Subject: Re: [RFC] Common clock framework for external clock generators

On Sun, May 13, 2012 at 06:30:55PM +0200, Sebastian Hesselbarh wrote:

> One question that remains from my original RFC is the missing
> clk_unregister() as i2c can be removed there also should be an
> function to unregister previously registered clocks?

One of the patches I've been sending adds a dummy clk_unregister() for
the sake of making the drivers look nicer - practically speaking it's
not likely to be terribly important as these things don't get unloaded
terribly often.  It looks like that patch didn't get applied either.

Mike's stuff is due to hit -next on Monday so I was planning to refresh
my driver and resend it then, probably with the unregister() though I'm
considering just removing the unregistration code to try to get make it
a bit more likely to get applied.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)