Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751829Ab1BZX2p (ORCPT ); Sat, 26 Feb 2011 18:28:45 -0500 Received: from mail-iy0-f174.google.com ([209.85.210.174]:56133 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751204Ab1BZX2n (ORCPT ); Sat, 26 Feb 2011 18:28:43 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=eTvdy/PujEdR61RTk6QNm2LcLaUy/B+ySqW9y1OJhjKDeGUH+LRS3vZmZwO+Zx2VPw +CsdrN7ud/jIuQENf2ca+l2huuN9/jI5lEX5v0BP6l2PNOjbcA2POOpku6FemOansTSQ sfpXUCRp/JOOmzONSZ+qL8JLvyZGGIxT/u5cc= MIME-Version: 1.0 In-Reply-To: References: <4D671556.80607@suse.com> <20110225060706.GA12723@merkur.ravnborg.org> <20110226221838.GA24028@merkur.ravnborg.org> Date: Sat, 26 Feb 2011 18:28:43 -0500 Message-ID: Subject: Re: [PATCH] Add ``cloneconfig'' target From: Arnaud Lacombe To: Sam Ravnborg Cc: Jeff Mahoney , Linux Kernel Mailing List , Roman Zippel , linux-kbuild@vger.kernel.org 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: 878 Lines: 22 Hi, On Sat, Feb 26, 2011 at 6:03 PM, Arnaud Lacombe wrote: >> The fact that the configuration is gzipped does not warrant >> a new option to deal with this that almost duplicate the >> existing functionality. >> > agree. > Let me precise, as there may be confusion. I agree about the new target issue, but definitively think this kconfig "option" (more a hack, which required a special option within kconfig) should be handled by Kbuild, not Kconfig, ie. I'd discard "option defconfig_list". File decompression (and eventually which config to pick) should be done prior to the invocation of Kconfig. - Arnaud -- 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/