[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpompxOpwi7fsy1m5UBxymR=dsVra3wvMcvziu7jd9iq8Ow@mail.gmail.com>
Date: Tue, 2 Apr 2013 06:19:35 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Tony Luck <tony.luck@...il.com>
Cc: Fenghua Yu <fenghua.yu@...el.com>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
arvind.chauhan@....com, robin.randhawa@....com,
Steve.Bannister@....com, Liviu.Dudau@....com,
charles.garcia-tobin@....com, cpufreq@...r.kernel.org,
Linux PM mailing list <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linaro-kernel@...ts.linaro.org, arnd.bergmann@...aro.org,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [PATCH 4/9] ia64: cpufreq: move cpufreq driver to drivers/cpufreq
On 2 April 2013 02:52, Tony Luck <tony.luck@...il.com> wrote:
> [Repost in plain text so the lists don't bounce it - curse you Gmail
> for switching to HTML]
Just to let others know how you fixed it: Above the compose area there
is a small button (or whatever you call it) which can show "Rich Formatting"
or "plain text". Click on that so that it shows "Rich Formatting" all the time.
>> Any comments on this patch?
>
> This part looks OK ... But is there a big finish later in the patch series where
> you unify some/all of the cpufreq code across architectures? By
> itself just moving
> bits from arch/ia64/kernel/cpufreq to drivers/cpufreq/ doesn't look to add
> much value.
There are people (including me) who tried various times to get things fixed/
consolidated in cpufreq area. They mostly worked over cleaning up stuff inside
drivers/cpufreq area rather then looking at complete kernel. To make that
path easy, this patchset is the first step: "Bring all of them together"..
After this more consolidation work may follow which will span all
cpufreq drivers.
One aspect would be to use cpufreq-cpu0 for whatever platform we can.
For now, your Ack will work :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists