Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754904Ab3HLH7h (ORCPT ); Mon, 12 Aug 2013 03:59:37 -0400 Received: from [213.199.154.209] ([213.199.154.209]:47088 "EHLO am1outboundpool.messaging.microsoft.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1754211Ab3HLH7e (ORCPT ); Mon, 12 Aug 2013 03:59:34 -0400 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI X-SpamScore: 3 X-BigFish: VS3(z1039mz98dI1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h8275dh1de097hz2dh87h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1fe8h1151h1155h) X-FB-DOMAIN-IP-MATCH: fail Date: Mon, 12 Aug 2013 15:58:24 +0800 From: Shawn Guo To: Viresh Kumar CC: , , , , , Subject: Re: [PATCH 13/44] cpufreq: cpu0: Use generic cpufreq routines Message-ID: <20130812075822.GF25061@S2101-09.ap.freescale.net> References: <3978525eb8c4b042fd399bb506d3d59960680538.1376116345.git.viresh.kumar@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <3978525eb8c4b042fd399bb506d3d59960680538.1376116345.git.viresh.kumar@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginatorOrg: sigmatel.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 17 On Sat, Aug 10, 2013 at 12:14:09PM +0530, Viresh Kumar wrote: > Most of the CPUFreq drivers do similar things in .exit() and .verify() routines > and .attr. So its better if we have generic routines for them which can be used > by cpufreq drivers then. > > This patch uses these generic routines for this driver. > > Cc: Shawn Guo > Signed-off-by: Viresh Kumar Acked-by: Shawn Guo -- 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/