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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120910001524.GL13739@n2100.arm.linux.org.uk>
Date:	Mon, 10 Sep 2012 01:15:24 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Lars-Peter Clausen <lars@...afoo.de>,
	Mike Turquette <mturquette@...com>,
	Greg Ungerer <gerg@...inux.org>,
	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 Mon, Sep 10, 2012 at 12:50:59AM +0100, Mark Brown wrote:
> 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.
> 
> I posted a patch for this (clk: Move devm_ APIs out of clkdev into
> HAVE_CLK) towards the end of the last release cycle and I think reposted
> it since and it had been sent to the patch tracker too (though I can't
> find any record of anything except the submission mail now).  It would
> be *really* good to get this merged.

Note that the patch system doesn't always return error messages anymore
(it used to do that reliably, but as it's now a favourite target for
spammers and was creating soo much backscatter, which was then filling
my mailbox with bounces... that had to change.)

However, it will always return a message for a patch that it adds to the
database, so if you don't get that then it means something went wrong
somewhere and you should check to see whether it exists in the database
in case it's the emailed response which got lost.

Email today still remains an unreliable transmission medium - there is
no guarantee that any message sent will get to its destination, and in
the same way, there is no guarantee that any acknowledgement (or NDR)
will get back to the originator.

> Who's looking after clkdev these days?  Mike doesn't seem to take
> patches as he's expecting Russell to take them which was happening for a
> while but I'm not sure that's the case any more, especially given
> Russell's followup here.  Due to the patch tracker the usual things for
> following up on unapplied patches don't work terribly well, it's much
> less likely that it's just an oversight there.

Well, in theory I'm the maintainer for clkdev and clk API, so I should
take the patch...
--
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/