Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754705AbaJHITo (ORCPT ); Wed, 8 Oct 2014 04:19:44 -0400 Received: from mail-oi0-f44.google.com ([209.85.218.44]:45551 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753236AbaJHITk (ORCPT ); Wed, 8 Oct 2014 04:19:40 -0400 MIME-Version: 1.0 In-Reply-To: <20141008101115.1835927a@free-electrons.com> References: <1412754534-14068-1-git-send-email-mturquette@linaro.org> <20141008101115.1835927a@free-electrons.com> Date: Wed, 8 Oct 2014 13:49:40 +0530 Message-ID: Subject: Re: [PATCH 0/2] allow cpufreq drivers to export flags From: Viresh Kumar To: Thomas Petazzoni Cc: Mike Turquette , "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:41, Thomas Petazzoni wrote: > On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote: >> 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 > Well, when one has to merge a large number of changes, we often > recommend to merge them piece by piece, which is what Mike is trying to > do here. So we cannot at the same time ask developers to merge things > in small pieces that are easy to review and to merge everything > together because the users of a given API are not there yet. >From the wording of Mike it looks like: - This is required by cpufreq drivers - today - And this will also be useful for scheduler The first point doesn't stand true anymore. Lets wait for Mike's reply and see his opinion. And then the patches are so small and there are no objections against them. I don't think getting them with the scheduler changes is that bad of an idea. In worst case, what if he has to redesign his idea? The new routines will stay without a caller then :) -- viresh -- 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/