Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757895Ab3DAGxV (ORCPT ); Mon, 1 Apr 2013 02:53:21 -0400 Received: from mail-db8lp0188.outbound.messaging.microsoft.com ([213.199.154.188]:10565 "EHLO db8outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757397Ab3DAGxT (ORCPT ); Mon, 1 Apr 2013 02:53:19 -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: -2 X-BigFish: VS-2(zz98dI1432Izz1f42h1fc6h1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275dhz2dh87h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1155h) X-FB-DOMAIN-IP-MATCH: fail Date: Mon, 1 Apr 2013 14:53:26 +0800 From: Shawn Guo To: Viresh Kumar CC: , , , , , , , , , , Subject: Re: [PATCH] cpufreq: cpufreq-cpu0: Call CPUFREQ_POSTCHANGE notifier for failure cases too Message-ID: <20130401065324.GF1693@S2101-09.ap.freescale.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginatorOrg: sigmatel.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 741 Lines: 17 On Sat, Mar 30, 2013 at 07:48:07PM +0530, Viresh Kumar wrote: > Currently we are simply returning from target() if we encounter some error after > broadcasting CPUFREQ_PRECHANGE notifier. Which looks to be wrong as others might > depend on POSTCHANGE notifier for their functioning. > > So, better broadcast CPUFREQ_POSTCHANGE notifier for these failure cases too, > but with old frequency. > > 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/