From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 11/44] cpufreq: at32ap: Use generic cpufreq routines
Date: Mon, 12 Aug 2013 21:11:21 +0200 [thread overview]
Message-ID: <20130812191121.GA18863@samfundet.no> (raw)
In-Reply-To: <CAKohpon=pRK9WX=BqPtN3gSZXBxX62J=PW4sbzUxsoc0fJGhkQ@mail.gmail.com>
Around Mon 12 Aug 2013 13:09:25 +0530 or thereabout, Viresh Kumar wrote:
> On 12 August 2013 13:00, Hans-Christian Egtvedt <egtvedt@samfundet.no> wrote:
>> I'll add it on my todo-list and have a look at it in the evening (-:
>
> Thanks.
>
>> How hard can it be™
>
> Its not about being hard but about knowing your platform well..
Turned out to be quite easy, but I couldn't get around to test it on
hardware (excuse: just moved, all HW is still in a box somewhere).
I'll submit the patch to cpufreq@vger.kernel.org for a sanity check, perhaps
you'll pull it into your series?
--
mvh
Hans-Christian Egtvedt
next prev parent reply other threads:[~2013-08-12 19:11 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 6:43 [PATCH 00/44] cpufreq: define generic routines for cpufreq drivers: for 3.13 Viresh Kumar
2013-08-10 6:43 ` [PATCH 01/44] cpufreq: arm_big_little: call cpufreq_frequency_table_put_attr() Viresh Kumar
2013-08-10 6:43 ` [PATCH 02/44] cpufreq: blackfin: " Viresh Kumar
2013-08-10 6:43 ` [PATCH 03/44] cpufreq: exynos: " Viresh Kumar
2013-08-12 6:18 ` Viresh Kumar
2013-08-18 10:00 ` amit daniel kachhap
2013-08-18 21:59 ` Kukjin Kim
2013-08-10 6:44 ` [PATCH 04/44] cpufreq: loongson2: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 05/44] cpufreq: omap: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 06/44] cpufreq: pxa: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 07/44] cpufreq: sparc: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 08/44] cpufreq: define generic .attr, .exit() and .verify() routines Viresh Kumar
2013-08-10 6:44 ` [PATCH 09/44] cpufreq: acpi: Use generic cpufreq routines Viresh Kumar
2013-08-10 6:44 ` [PATCH 10/44] cpufreq: arm_big_little: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 11/44] cpufreq: at32ap: " Viresh Kumar
2013-08-10 8:23 ` Hans-Christian Egtvedt
2013-08-12 6:07 ` Viresh Kumar
2013-08-12 7:10 ` Hans-Christian Egtvedt
2013-08-12 7:13 ` Viresh Kumar
2013-08-12 7:30 ` Hans-Christian Egtvedt
2013-08-12 7:39 ` Viresh Kumar
2013-08-12 19:11 ` Hans-Christian Egtvedt [this message]
2013-08-13 4:54 ` Viresh Kumar
2013-08-10 6:44 ` [PATCH 12/44] cpufreq: blackfin: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 13/44] cpufreq: cpu0: " Viresh Kumar
2013-08-12 7:58 ` Shawn Guo
2013-08-10 6:44 ` [PATCH 14/44] cpufreq: cris: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 15/44] cpufreq: davinci: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 16/44] cpufreq: dbx500: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 17/44] cpufreq: e_powersaver: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 18/44] cpufreq: elanfreq: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 19/44] cpufreq: exynos: " Viresh Kumar
2013-08-18 10:03 ` amit daniel kachhap
2013-08-18 22:00 ` Kukjin Kim
2013-08-10 6:44 ` [PATCH 20/44] cpufreq: ia64-acpi: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 21/44] cpufreq: imx6q: " Viresh Kumar
2013-08-12 7:58 ` Shawn Guo
2013-08-12 8:10 ` Viresh Kumar
2013-08-12 8:34 ` Shawn Guo
2013-08-10 6:44 ` [PATCH 22/44] cpufreq: kirkwood: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 23/44] cpufreq: longhaul: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 24/44] cpufreq: loongson2: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 25/44] cpufreq: maple: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 26/44] cpufreq: omap: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 27/44] cpufreq: p4-clockmod: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 28/44] cpufreq: pasemi: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 29/44] cpufreq: pcc: " Viresh Kumar
2013-08-12 6:08 ` Viresh Kumar
2013-08-10 6:44 ` [PATCH 30/44] cpufreq: pmac: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 31/44] cpufreq: powernow: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 32/44] cpufreq: ppc-corenet: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 33/44] cpufreq: ppc_cbe: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 34/44] cpufreq: pxa: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 35/44] cpufreq: s3cx4xx: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 36/44] cpufreq: s5pv210: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 37/44] cpufreq: sc520: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 38/44] cpufreq: sh: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 39/44] cpufreq: sparc: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 40/44] cpufreq: spear: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 41/44] cpufreq: speedstep: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 42/44] cpufreq: tegra: " Viresh Kumar
2013-08-10 6:44 ` [PATCH 43/44] cpufreq: unicore2: " Viresh Kumar
2013-08-12 6:08 ` Viresh Kumar
2013-08-10 6:44 ` [PATCH 44/44] cpufreq: pass suitable index instead of freq to cpufreq_driver->target() Viresh Kumar
2013-08-10 7:45 ` Viresh Kumar
2013-08-12 6:50 ` Viresh Kumar
2013-08-10 7:46 ` [PATCH 00/44] cpufreq: define generic routines for cpufreq drivers: for 3.13 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=20130812191121.GA18863@samfundet.no \
--to=egtvedt@samfundet.no \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.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).