Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750832Ab3HSEkJ (ORCPT ); Mon, 19 Aug 2013 00:40:09 -0400 Received: from mail-oa0-f41.google.com ([209.85.219.41]:51642 "EHLO mail-oa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750769Ab3HSEkG (ORCPT ); Mon, 19 Aug 2013 00:40:06 -0400 MIME-Version: 1.0 In-Reply-To: References: <14993d27bdc6a91eced0af5eb96bdb5ca6546cbf.1376619363.git.viresh.kumar@linaro.org> Date: Mon, 19 Aug 2013 10:10:05 +0530 Message-ID: Subject: Re: [PATCH 13/34] cpufreq: exynos5440: set CPUFREQ_NO_NOTIFICATION flag From: Viresh Kumar To: amit daniel kachhap Cc: "Rafael J. Wysocki" , linaro-kernel , "patches@linaro.org" , "cpufreq@vger.kernel.org" , "linux-pm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , LAK , Kukjin Kim Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 615 Lines: 14 On 19 August 2013 09:12, amit daniel kachhap wrote: >>> + .flags = CPUFREQ_STICKY | CPUFREQ_NO_NOTIFICATION, > How about naming the flag as CPUFREQ_ASYNC_NOTIFICATION? For platforms > not defining this flag, the notifiers can be called synchronously from > the core driver. Nice.. +1 My repo will be updated with this change.. -- 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/