From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-bw0-f46.google.com ([209.85.214.46]:61969 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752190Ab0GNJNX convert rfc822-to-8bit (ORCPT ); Wed, 14 Jul 2010 05:13:23 -0400 MIME-Version: 1.0 In-Reply-To: <201007121634.04427.davidb@codeaurora.org> References: <201007121605.32462.davidb@codeaurora.org> <201007121634.04427.davidb@codeaurora.org> Date: Wed, 14 Jul 2010 12:13:07 +0300 Message-ID: Subject: Re: ARM defconfig files From: Felipe Contreras Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: David Brown Cc: Linus Torvalds , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , Russell King - ARM Linux , Daniel Walker , Kevin Hilman , Linux Kernel Mailing List , linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Grant Likely , Eric Miao , linux-omap@vger.kernel.org, Nicolas Pitre On Tue, Jul 13, 2010 at 2:34 AM, David Brown wrote: > It seems a bit brute force, probably not something I can make part of > our regular build process, but I can definitely run it before sending > patches out. > > I wonder if there's a more efficient way of doing it that doesn't > involve invoking make for each line of the file.  It at least > shouldn't be necessary to actually build the kernel each time. Yes, I think there's a more efficient way to do it, but it would require the SAT resolver, or something like that. -- Felipe Contreras