From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755545AbcJTD3g (ORCPT <rfc822;w@1wt.eu>);
        Wed, 19 Oct 2016 23:29:36 -0400
Received: from mail-pf0-f180.google.com ([209.85.192.180]:34582 "EHLO
        mail-pf0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751519AbcJTD3e (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 19 Oct 2016 23:29:34 -0400
Date: Thu, 20 Oct 2016 08:59:30 +0530
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Tim Walberg <twalberg@comcast.net>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>, linux-kernel@vger.kernel.org,
        Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: 4.8.1 regression with cpufreq governors
Message-ID: <20161020032930.GC11766@vireshk-i7>
References: <20161018004606.GA5559@comcast.net>
 <2549240.nvakNXlyKF@vostro.rjw.lan>
 <20161019200610.GB9047@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20161019200610.GB9047@comcast.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 19-10-16, 15:06, Tim Walberg wrote:
> This indeed turned out to be the fix.

Really? How can this fix the ondemand governor thing?

Or is it that Ondemand never broke ?

-- 
viresh