From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752217AbcEPEzO (ORCPT ); Mon, 16 May 2016 00:55:14 -0400 Received: from mail-pf0-f174.google.com ([209.85.192.174]:33558 "EHLO mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751967AbcEPEzM (ORCPT ); Mon, 16 May 2016 00:55:12 -0400 Date: Mon, 16 May 2016 10:25:09 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Linux PM list , Srinivas Pandruvada , Linux Kernel Mailing List Subject: Re: [PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events Message-ID: <20160516045509.GP9296@vireshk-i7> References: <10707470.yIcqGAzuFY@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10707470.yIcqGAzuFY@vostro.rjw.lan> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14-05-16, 00:58, Rafael J. Wysocki wrote: > Hi, > > This series is on top of the current linux-next witn the following two patches > applied: > > https://patchwork.kernel.org/patch/9080801/ > https://patchwork.kernel.org/patch/9080791/ > > It cleans up a few things and then reworks the governor API to get rid of > governor events and use callbacks representing individual governor operations > (init, exit, start, stop, limits update) instead. > > I'm regarding it as v4.8 material, but I'd like to put it into linux-next as > soon as 4.7-rc1 is out so subsequent cpufreq development happens on top of it. > > It has been lightly tested without any problems showing up so far. Acked-by: Viresh Kumar -- viresh