From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: linux-tegra@vger.kernel.org,
Mike Turquette <mturquette@linaro.org>,
Joseph Lo <josephl@nvidia.com>,
Paul Walmsley <pwalmsley@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: replace enum tegra114_clk by binding header
Date: Tue, 03 Sep 2013 11:57:05 -0600 [thread overview]
Message-ID: <522622F1.70008@wwwdotorg.org> (raw)
In-Reply-To: <1378213915-10222-1-git-send-email-pdeschrijver@nvidia.com>
On 09/03/2013 07:11 AM, Peter De Schrijver wrote:
> As the clock IDs are now specified in a header file, we can use those
> definitions instead of maintaining an internal enum.
Acked-by: Stephen Warren <swarren@nvidia.com>
I assume this will go through Mike's clock tree for 3.13.
I assume similar patches will follow for Tegra20/30?
next prev parent reply other threads:[~2013-09-03 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 13:11 [PATCH] clk: tegra: replace enum tegra114_clk by binding header Peter De Schrijver
2013-09-03 17:57 ` Stephen Warren [this message]
2013-10-04 15:52 ` Peter De Schrijver
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=522622F1.70008@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=josephl@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=pwalmsley@nvidia.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