From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: cpufreq: frequency scaling spec in DT node
Date: Wed, 12 Jul 2017 19:38:04 +0530 [thread overview]
Message-ID: <20170712140804.GG1679@vireshk-i7> (raw)
In-Reply-To: <19d1613b-aea0-1ddf-e5b4-11e027402de1@free.fr>
On 12-07-17, 13:25, Mason wrote:
> I will test your patch on my 4.9 branch.
>
> Does tango-cpufreq.c look acceptable to you?
> (I am aware the patch needs work in the the Kconfig/Makefile part.
> That was quick and dirty.)
Mostly yes. Just make sure everything is well handled when u send it.
--
viresh
next prev parent reply other threads:[~2017-07-12 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 9:48 cpufreq: frequency scaling spec in DT node Mason
2017-06-29 10:04 ` Viresh Kumar
2017-06-29 11:41 ` Mason
2017-06-29 13:01 ` Mason
2017-06-29 14:35 ` Viresh Kumar
2017-06-29 14:34 ` Viresh Kumar
2017-07-11 9:27 ` Mason
2017-07-11 10:25 ` Viresh Kumar
2017-07-11 11:09 ` Mason
2017-07-11 11:56 ` Mason
2017-07-12 3:41 ` Viresh Kumar
2017-07-12 9:58 ` Mason
2017-07-12 10:09 ` Viresh Kumar
2017-07-12 11:25 ` Mason
2017-07-12 14:08 ` Viresh Kumar [this message]
2017-07-11 13:36 ` Mason
2017-07-12 3:56 ` Viresh Kumar
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=20170712140804.GG1679@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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