From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clkdev: Implement managed clk_get()
Date: Mon, 2 Apr 2012 22:59:28 +0100 [thread overview]
Message-ID: <20120402215927.GG3160@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120402215341.GL24211@n2100.arm.linux.org.uk>
On Mon, Apr 02, 2012 at 10:53:41PM +0100, Russell King - ARM Linux wrote:
> On Mon, Apr 02, 2012 at 10:49:45PM +0100, Mark Brown wrote:
> > +CLOCK
> > + devm_clk_get()
> devm_clk_put() ?
Yeah, I noticed that immediately after I sent when it turned up in my
inbox and have already fixed locally - it'll be in any future version
I send out.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120402/60805c4e/attachment.sig>
next prev parent reply other threads:[~2012-04-02 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 21:49 [PATCH] clkdev: Implement managed clk_get() Mark Brown
2012-04-02 21:53 ` Russell King - ARM Linux
2012-04-02 21:59 ` Mark Brown [this message]
2012-04-04 17:48 ` Thierry Reding
2012-04-04 19:21 ` Mark Brown
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=20120402215927.GG3160@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).