Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758692Ab3DAVW4 (ORCPT ); Mon, 1 Apr 2013 17:22:56 -0400 Received: from mail-vc0-f178.google.com ([209.85.220.178]:62890 "EHLO mail-vc0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755972Ab3DAVWy (ORCPT ); Mon, 1 Apr 2013 17:22:54 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 1 Apr 2013 14:22:53 -0700 Message-ID: Subject: Re: [PATCH 4/9] ia64: cpufreq: move cpufreq driver to drivers/cpufreq From: Tony Luck To: Viresh Kumar Cc: Fenghua Yu , "linux-ia64@vger.kernel.org" , arvind.chauhan@arm.com, robin.randhawa@arm.com, Steve.Bannister@arm.com, Liviu.Dudau@arm.com, charles.garcia-tobin@arm.com, cpufreq@vger.kernel.org, Linux PM mailing list , Linux Kernel Mailing List , linaro-kernel@lists.linaro.org, arnd.bergmann@linaro.org, "Rafael J. Wysocki" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 628 Lines: 17 [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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/