[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+8MBbLwxiPPvyKyQNEDSbNKthpAmooKVe7b+pg-NCETOkSLPA@mail.gmail.com>
Date: Mon, 1 Apr 2013 14:22:53 -0700
From: Tony Luck <tony.luck@...il.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
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
[Repost in plain text so the lists don't bounce it - curse you Gmail
for switching to HTML]
> 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.
-Tony
--
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