From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5D631C7618B for ; Thu, 25 Jul 2019 13:36:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2C5EC22C7D for ; Thu, 25 Jul 2019 13:36:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564061798; bh=P14qZ4ZPdWg+EwZRpeIuk270A0Co0pdknb9KeS6lC4o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=T4lbcXdmbgPBG4vLY6AZDKGBjltQSgDat2kpXTvacOWEid/7rGP9VVP0Hg0IPrhH7 N1P+bZpsVI7rYxlUVZscx5IlTnOAvDxmlvrAb/8jbAsIm4RVmcoSG2QXbvOtXfcUD2 ZiQEg4fmX3xsLeOwyimh1cfhdKKX0doUzZPX/FL0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388928AbfGYNgh (ORCPT ); Thu, 25 Jul 2019 09:36:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:46692 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388905AbfGYNgh (ORCPT ); Thu, 25 Jul 2019 09:36:37 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 19F7B21901; Thu, 25 Jul 2019 13:36:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564061796; bh=P14qZ4ZPdWg+EwZRpeIuk270A0Co0pdknb9KeS6lC4o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=r6bpJHz6DFdt5uEwrs27i+gAFHPJru5oJr7PTkquA28Ocz9PtQRkwMqgvyNuukZ4W 6TApLTf63pgqo2x9w5WCxfFbspZYQYIubWztcYb9W1LVXizSRGqDPLpb1jW4bTNi3A hEEYUOBoJZz5sCm1jyF0sjT7QnRMU5Alu+8X0FvI= Date: Thu, 25 Jul 2019 15:36:34 +0200 From: Greg Kroah-Hartman To: Viresh Kumar Cc: Rafael Wysocki , "Rafael J. Wysocki" , linux-pm@vger.kernel.org, Vincent Guittot , linux-kernel@vger.kernel.org Subject: Re: [PATCH V2 06/10] arch_topology: Use CPUFREQ_CREATE_POLICY instead of CPUFREQ_NOTIFY Message-ID: <20190725133634.GA11115@kroah.com> References: <3afc5046ba9435d229a004c17b005197488006d4.1563862014.git.viresh.kumar@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3afc5046ba9435d229a004c17b005197488006d4.1563862014.git.viresh.kumar@linaro.org> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Tue, Jul 23, 2019 at 11:44:06AM +0530, Viresh Kumar wrote: > CPUFREQ_NOTIFY is going to get removed soon, lets use > CPUFREQ_CREATE_POLICY instead of that here. CPUFREQ_CREATE_POLICY is > called only once (which is exactly what we want here) for each cpufreq > policy when it is first created. > > Signed-off-by: Viresh Kumar > --- > drivers/base/arch_topology.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Acked-by: Greg Kroah-Hartman