Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754628AbaJHHye (ORCPT ); Wed, 8 Oct 2014 03:54:34 -0400 Received: from mail-oi0-f52.google.com ([209.85.218.52]:46620 "EHLO mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754226AbaJHHyc (ORCPT ); Wed, 8 Oct 2014 03:54:32 -0400 MIME-Version: 1.0 In-Reply-To: <1412754534-14068-1-git-send-email-mturquette@linaro.org> References: <1412754534-14068-1-git-send-email-mturquette@linaro.org> Date: Wed, 8 Oct 2014 13:24:30 +0530 Message-ID: Subject: Re: [PATCH 0/2] allow cpufreq drivers to export flags From: Viresh Kumar To: Mike Turquette Cc: Thomas Petazzoni , "Rafael J. Wysocki" , Lists linaro-kernel , "linux-pm@vger.kernel.org" , Shawn Guo , Stephen Boyd , "linux-arm-msm@vger.kernel.org" , Sachin Kamat , "pramod.gurav@smartplayin.com" , Rob Herring , Ezequiel Garcia , Tawfik Bayouk , Nadav Haklai , Lior Amsalem , Morten Rasmussen , Dietmar Eggemann , Vincent Guittot , Nicolas Pitre , Linux Kernel Mailing List , Tuukka Tikkanen Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8 October 2014 13:18, Mike Turquette wrote: > This series is partially in response to a discussion around DT bindings > for CPUfreq drivers [0], but it is also needed for on-going work to > integrate CPUfreq with the scheduler. In particular a scheduler-driven > cpu frequency scaling policy would be well served to know if the > underlying CPUfreq driver .target callback might sleep or block for a > long time. > > [0] http://lkml.kernel.org/r/ Firstly this link is broken and then the last comment I gave in Thomas's thread was that he doesn't need this routine anymore. And so your scheduler work is the only user of it.. And so probably we should get this included with the scheduler patches only, isn't it? Just including them without any user wouldn't benefit.. Or am I missing something ? -- 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/