Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752119AbaDYPLa (ORCPT ); Fri, 25 Apr 2014 11:11:30 -0400 Received: from sema.semaphore.gr ([78.46.194.137]:59035 "EHLO sema.semaphore.gr" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751217AbaDYPLZ (ORCPT ); Fri, 25 Apr 2014 11:11:25 -0400 Message-ID: <535A7B18.9070505@semaphore.gr> Date: Fri, 25 Apr 2014 18:11:20 +0300 From: Stratos Karafotis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Prabhakar Lad CC: "Rafael J. Wysocki" , Viresh Kumar , Kukjin Kim , linux-pm@vger.kernel.org, LKML , "cpufreq@vger.kernel.org" , linux-samsung-soc , Sudeep Holla , Olof Johansson , linuxppc-dev@lists.ozlabs.org, "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH v4 2/8] cpufreq: Use cpufreq_for_each_* macros for frequency table iteration References: <534DB1EB.1080401@semaphore.gr> <5355A327.3020308@semaphore.gr> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Prabhakar, On 25/04/2014 03:31 μμ, Prabhakar Lad wrote: > Hi Stratos, > > Thanks for the patch. > > On Tue, Apr 22, 2014 at 4:30 AM, Stratos Karafotis > wrote: >> The cpufreq core now supports the cpufreq_for_each_entry and >> cpufreq_for_each_valid_entry macros helpers for iteration over the >> cpufreq_frequency_table, so use them. >> >> It should have no functional changes. >> > This patch produces following build warning, > > drivers/cpufreq/freq_table.c: In function 'cpufreq_frequency_table_cpuinfo': > drivers/cpufreq/freq_table.c:36:3: warning: format '%lu' expects > argument of type 'long unsigned int', but argument 2 has type 'int' > [-Wformat=] > pr_debug("table entry %lu: %u kHz\n", pos - table, freq); Thanks for this finding. I will fix it and resend the patch. Stratos Karafotis -- 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/