From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751799AbcFFHHz (ORCPT <rfc822;w@1wt.eu>);
	Mon, 6 Jun 2016 03:07:55 -0400
Received: from mailout1.w1.samsung.com ([210.118.77.11]:22358 "EHLO
	mailout1.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751112AbcFFHHw (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 6 Jun 2016 03:07:52 -0400
X-AuditID: cbfec7f5-f792a6d000001302-50-5755214538f5
Subject: Re: [PATCH V3 4/9] cpufreq: exynos: Use 'index' only to index into
 policy->freq_table
To: Viresh Kumar <viresh.kumar@linaro.org>, Rafael Wysocki <rjw@rjwysocki.net>,
        Kukjin Kim <kgene@kernel.org>
References: <cover.1464960877.git.viresh.kumar@linaro.org>
 <e6621408b2a7748d6b984eb6c97d8ee13be96ad5.1464960877.git.viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
        linux-kernel@vger.kernel.org, steve.muckle@linaro.org,
        linux-arm-kernel@lists.infradead.org,
        linux-samsung-soc@vger.kernel.org,
        Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
        Shawn Guo <shawn.guo@freescale.com>, Steven Miao <realmz6@gmail.com>
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Message-id: <57552144.10300@samsung.com>
Date: Mon, 06 Jun 2016 09:07:48 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.8.0
MIME-version: 1.0
In-reply-to: <e6621408b2a7748d6b984eb6c97d8ee13be96ad5.1464960877.git.viresh.kumar@linaro.org>
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupikeLIzCtJLcpLzFFi42I5/e/4NV1XxdBwg7aVUhaTnrxntnj9wtCi
	//FrZov3h54xW2x6fI3V4vKuOWwWn3uPMFrMOL+PyWLnxwVsFmdOX2K1WNbSxmLx9kUzs8XG
	rx4OvB7/DvczeeycdZfdY9OqTjaPO9f2sHlsXlLvcfvfY2aPLVfbWTz6tqxi9Pi8SS6AM4rL
	JiU1J7MstUjfLoEr48Cjr6wFE9gqFkx/ytrA2MXaxcjJISFgIvF98TIWCFtM4sK99WwgtpDA
	UkaJfxdUuhi5gOxnjBLPV30HaxAWSJA439cEZosI5Es8753FDlHUxyixpvckM4jDLLCLSeLO
	m+NgY9kEjCU2L18CNpZXQEOiueUimM0ioCrxs+0DM4gtKhAhMWv7DyaIGkGJH5PvgfVyAm3r
	nb8VqIYDaKiexP2LWiBhZgF5ic1r3jJPYBSYhaRjFkLVLCRVCxiZVzGKppYmFxQnpeca6RUn
	5haX5qXrJefnbmKExNDXHYxLj1kdYhTgYFTi4WUoCgkXYk0sK67MPcQowcGsJMJ7RSI0XIg3
	JbGyKrUoP76oNCe1+BCjNAeLkjjvzF3vQ4QE0hNLUrNTUwtSi2CyTBycUg2M4eGnVk9Ls6/e
	0jFZydMt/N4R/qzizDU75ibc/Bhz6q/xdMOiaCUHizsrp1w5b7tp1kGRU+7Hlhwo/nnOYf93
	9dbuygM3j30Jm/w9uHOPcre1byrX249629+d003dtMPAPLrtCJ+HdaD/N56t6vtrXYOjixle
	9zkydz+Ss/GYd/TDuUeiB6b+UmIpzkg01GIuKk4EADIoJ/SdAgAA
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 06/03/2016 03:35 PM, Viresh Kumar wrote:
> Later patches would make changes in cpufreq core, after which
> policy->freq_table may be reordered by cpufreq core and it wouldn't be
> safe anymore to use 'index' for any other local arrays.
> 
> To prepare for that, use policy->freq_table[index].driver_data for other
> driver specific usage of 'index'. The 'driver_data' fields are already
> set properly by the driver.
> 
> Cc: Kukjin Kim <kgene@kernel.org>
> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  drivers/cpufreq/exynos5440-cpufreq.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)

Acked-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>

Best regards,
Krzysztof