From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 8/9] ASoC: tegra: add clk_prepare/clk_unprepare
Date: Fri, 8 Jun 2012 09:02:08 +0800 [thread overview]
Message-ID: <20120608010207.GB10455@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1338870583-8704-9-git-send-email-pgaikwad@nvidia.com>
On Tue, Jun 05, 2012 at 09:59:42AM +0530, Prashant Gaikwad wrote:
> Use clk_prepare/clk_unprepare as required by the generic clk framework.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
-------------- 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/20120608/841fc67b/attachment.sig>
next prev parent reply other threads:[~2012-06-08 1:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 4:29 [PATCH v3 0/9] Add clk_prepare/clk_unprepare Prashant Gaikwad
2012-06-05 4:29 ` [PATCH v3 1/9] ARM: tegra: add clk_prepare/clk_unprepare Prashant Gaikwad
2012-06-05 4:29 ` [PATCH v3 2/9] i2c: tegra: Add clk_prepare/clk_unprepare Prashant Gaikwad
2012-06-05 4:29 ` [PATCH v3 3/9] mmc: tegra: add clk_prepare/clk_unprepare Prashant Gaikwad
2012-06-05 4:29 ` [PATCH v3 4/9] USB: ehci-tegra: " Prashant Gaikwad
2012-06-05 4:29 ` [PATCH v3 5/9] Input: tegra-kbc - " Prashant Gaikwad
2012-06-12 7:30 ` Dmitry Torokhov
2012-06-05 4:29 ` [PATCH v3 6/9] spi/tegra: " Prashant Gaikwad
2012-06-05 4:29 ` [PATCH v3 7/9] staging: nvec: " Prashant Gaikwad
2012-06-08 19:48 ` Marc Dietrich
2012-06-05 4:29 ` [PATCH v3 8/9] ASoC: tegra: " Prashant Gaikwad
2012-06-08 1:02 ` Mark Brown [this message]
2012-06-08 4:43 ` Pankaj Jangra
2012-06-08 4:54 ` Prashant Gaikwad
2012-06-05 4:29 ` [PATCH v3 9/9] crypto: " Prashant Gaikwad
2012-06-12 8:10 ` Herbert Xu
2012-06-11 18:04 ` [PATCH v3 0/9] Add clk_prepare/clk_unprepare Stephen Warren
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=20120608010207.GB10455@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).