From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: Enable CPUFreq support for Tegra124 Chromebooks
Date: Tue, 15 Sep 2015 10:12:36 +0200 [thread overview]
Message-ID: <20150915081234.GA25970@ulmo.nvidia.com> (raw)
In-Reply-To: <CAAObsKA0N50gfPA9sMZfnM8N+N9Oo-YHMCDdF7JdWjpxXtFJbA@mail.gmail.com>
On Thu, Sep 03, 2015 at 03:40:45PM +0200, Tomeu Vizoso wrote:
> On 13 July 2015 at 15:08, Jon Hunter <jonathanh@nvidia.com> wrote:
> > On 03/06/15 12:44, Jon Hunter wrote:
> >> Adding LAKML. Jon
> >>
> >> On 03/06/15 12:43, Jon Hunter wrote:
> >>> Add the device-tree DFLL clock node and CPU regulator phandle for
> >>> tegra124 chromebooks to enable CPUFreq support on these boards.
>
> Ping.
>
> Thanks,
Sorry that this has gone unnoticed for so long. I've applied it now to
the for-4.4/dt branch.
Tomeu, do you want me to add your Tested-by, Reviewed-by or Acked-by
before I push this out?
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150915/40189def/attachment.sig>
next prev parent reply other threads:[~2015-09-15 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1433331821-9648-1-git-send-email-jonathanh@nvidia.com>
2015-06-03 11:44 ` [PATCH] ARM: tegra: Enable CPUFreq support for Tegra124 Chromebooks Jon Hunter
2015-07-13 13:08 ` Jon Hunter
2015-09-03 13:40 ` Tomeu Vizoso
2015-09-15 8:12 ` Thierry Reding [this message]
2015-09-15 9:00 ` Tomeu Vizoso
2015-11-04 12:16 ` Jon Hunter
2015-11-04 12:19 ` Jon Hunter
2015-11-04 13:23 ` Jon Hunter
2015-11-20 15:20 ` Jon Hunter
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=20150915081234.GA25970@ulmo.nvidia.com \
--to=thierry.reding@gmail.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).