Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752395Ab3HTGdU (ORCPT ); Tue, 20 Aug 2013 02:33:20 -0400 Received: from mail-oa0-f44.google.com ([209.85.219.44]:37988 "EHLO mail-oa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752139Ab3HTGdS (ORCPT ); Tue, 20 Aug 2013 02:33:18 -0400 MIME-Version: 1.0 In-Reply-To: <6607838.UAT3ZUDseh@vostro.rjw.lan> References: <1582060.zfvsylJcxu@vostro.rjw.lan> <6607838.UAT3ZUDseh@vostro.rjw.lan> Date: Tue, 20 Aug 2013 12:03:17 +0530 Message-ID: Subject: Re: [PATCH V2 07/11] cpufreq: Use cpufreq_policy_list for iterating over policies From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Lists linaro-kernel , Patch Tracking , "cpufreq@vger.kernel.org" , "linux-pm@vger.kernel.org" , Linux Kernel Mailing List , "Srivatsa S. Bhat" 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: 941 Lines: 16 On 20 August 2013 04:52, Rafael J. Wysocki wrote: > From my experience, however, it is good to figure out what needs to be included > into your test kernel and configure away everything else. Also, I'd recommend > to build as much as possible into the kernel image and avoid compiling too many > modules, because installing modules takes time too (ideally, if you can get > away without any modules at all, that's the best option timing-wise). Just > select only the drivers that you're going to use and unset all of the options > that don't apply to your test machine. I haven't done this exercise yet but I have a workable solution with default .config as suggested by Amit :) -- 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/