From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965799AbbJ1P2S (ORCPT ); Wed, 28 Oct 2015 11:28:18 -0400 Received: from mail-pa0-f53.google.com ([209.85.220.53]:36763 "EHLO mail-pa0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755482AbbJ1P2Q (ORCPT ); Wed, 28 Oct 2015 11:28:16 -0400 Date: Wed, 28 Oct 2015 20:58:11 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, open list Subject: Re: [PATCH V3 2/5] cpufreq: ondemand: update sampling rate immediately Message-ID: <20151028152811.GE3716@ubuntu> References: <2498053.EX0k8RstLZ@vostro.rjw.lan> <20151028093109.GJ30039@ubuntu> <3215277.8YKq8PWCpx@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3215277.8YKq8PWCpx@vostro.rjw.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28-10-15, 16:31, Rafael J. Wysocki wrote: > Is the current code really problematic? Its not problematic, but just that I didn't like special code written here. Also, its a blocker for the next patch which tries to schedule work on all the policy->cpus together. -- viresh