Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752984Ab3HMEyw (ORCPT ); Tue, 13 Aug 2013 00:54:52 -0400 Received: from mail-ob0-f176.google.com ([209.85.214.176]:63974 "EHLO mail-ob0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751457Ab3HMEyu convert rfc822-to-8bit (ORCPT ); Tue, 13 Aug 2013 00:54:50 -0400 MIME-Version: 1.0 In-Reply-To: <20130812191121.GA18863@samfundet.no> References: <20130810082333.GA27640@samfundet.no> <20130812071042.GA30670@samfundet.no> <20130812073058.GA7776@samfundet.no> <20130812191121.GA18863@samfundet.no> Date: Tue, 13 Aug 2013 10:24:50 +0530 Message-ID: Subject: Re: [PATCH 11/44] cpufreq: at32ap: Use generic cpufreq routines From: Viresh Kumar To: Hans-Christian Egtvedt 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 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1014 Lines: 26 On 13 August 2013 00:41, Hans-Christian Egtvedt wrote: > Around Mon 12 Aug 2013 13:09:25 +0530 or thereabout, Viresh Kumar wrote: >> On 12 August 2013 13:00, Hans-Christian Egtvedt 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 had a quick look at it and yes it is pretty much hadware specific :) Thanks. > I'll submit the patch to cpufreq@vger.kernel.org for a sanity check, perhaps > you'll pull it into your series? Yes, I will. -- 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/