Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758468Ab3GZKOd (ORCPT ); Fri, 26 Jul 2013 06:14:33 -0400 Received: from mail-oa0-f50.google.com ([209.85.219.50]:41490 "EHLO mail-oa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756558Ab3GZKOa (ORCPT ); Fri, 26 Jul 2013 06:14:30 -0400 MIME-Version: 1.0 In-Reply-To: <1374770011-22171-2-git-send-email-l.majewski@samsung.com> References: <1370502472-7249-1-git-send-email-l.majewski@samsung.com> <1374770011-22171-1-git-send-email-l.majewski@samsung.com> <1374770011-22171-2-git-send-email-l.majewski@samsung.com> Date: Fri, 26 Jul 2013 15:44:29 +0530 Message-ID: Subject: Re: [PATCH v6 1/8] cpufreq: Store cpufreq policies in a list From: Viresh Kumar To: Lukasz Majewski Cc: "Rafael J. Wysocki" , Zhang Rui , Eduardo Valentin , "cpufreq@vger.kernel.org" , Linux PM list , Jonghwa Lee , Lukasz Majewski , linux-kernel , Bartlomiej Zolnierkiewicz , Daniel Lezcano , Kukjin Kim , Myungjoo Ham , durgadoss.r@intel.com 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: 981 Lines: 27 On 25 July 2013 22:03, Lukasz Majewski wrote: > Policies available in a cpufreq framework are now linked together. They are > accessible via cpufreq_policy_list defined at cpufreq core. > > Signed-off-by: Lukasz Majewski > Signed-off-by: Myungjoo Ham Looks good but would have been better if you could have moved existing code to use this infrastructure.. For example, this code in __cpufreq_add_dev() #ifdef CONFIG_HOTPLUG_CPU /* Check if this cpu was hot-unplugged earlier and has siblings */ read_lock_irqsave(&cpufreq_driver_lock, flags); for_each_online_cpu(sibling) { --- } read_unlock_irqrestore(&cpufreq_driver_lock, flags); #endif -- 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/