From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Mike Turquette <mturquette@ti.com>,
Russell King <linux@arm.linux.org.uk>,
Greg Ungerer <gerg@uclinux.org>,
Julia Lawall <julia.lawall@lip6.fr>,
Artem Bityutskiy <dedekind1@gmail.com>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: Make the managed clk functions generically available
Date: Mon, 10 Sep 2012 00:50:59 +0100 [thread overview]
Message-ID: <20120909235059.GA2643@sirena.org.uk> (raw)
In-Reply-To: <1347202862-1617-1-git-send-email-lars@metafoo.de>
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.
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.
next prev parent reply other threads:[~2012-09-09 23:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 15:01 Lars-Peter Clausen
2012-09-09 20:57 ` Russell King - ARM Linux
2012-09-09 23:50 ` Mark Brown [this message]
2012-09-10 0:15 ` Russell King - ARM Linux
2012-09-10 0:20 ` Mark Brown
2012-09-10 0:39 ` Russell King - ARM Linux
2012-09-11 14:44 ` Lars-Peter Clausen
2012-09-11 14:50 ` Artem Bityutskiy
2012-09-12 1:32 ` Greg Ungerer
2012-09-12 20:43 ` Lars-Peter Clausen
2012-09-15 21:31 ` Russell King - ARM Linux
2012-09-16 0:15 ` Greg Ungerer
2012-09-18 8:00 ` Thierry Reding
2012-09-18 9:35 ` Russell King - ARM Linux
2012-09-18 11:25 ` Thierry Reding
2012-09-18 20:40 ` Russell King - ARM Linux
2012-09-19 6:55 ` Thierry Reding
2012-09-11 17:51 ` Russell King - ARM Linux
2012-09-10 3:10 ` Greg Ungerer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120909235059.GA2643@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dedekind1@gmail.com \
--cc=gerg@uclinux.org \
--cc=julia.lawall@lip6.fr \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome