Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755544Ab1EPUYT (ORCPT ); Mon, 16 May 2011 16:24:19 -0400 Received: from mail-iw0-f174.google.com ([209.85.214.174]:57999 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752988Ab1EPUYR (ORCPT ); Mon, 16 May 2011 16:24:17 -0400 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=chYMvK5CIiL7FfiV6shvxONIn/xByfVVIWBwSSk171BUW+I5UNe9s9FgUL3OyafMvp p/7rIQhscy0nhaK6B53IyEpHivtwViLgsQqkNdt8KHr0f4VCKJYSSYqlmfBU8o7YpFWT s1PuTDtEYY0qFvfHmleBfBMoIX9OoA6/gsWAQ= MIME-Version: 1.0 In-Reply-To: <4DD1838D.7030305@suse.cz> References: <1304658229-30820-1-git-send-email-plagnioj@jcrosoft.com> <20110507015041.GA21017@game.jcrosoft.org> <4DC7AB57.9050002@suse.cz> <20110513080909.GO18952@game.jcrosoft.org> <32557.1305572616@localhost> <4DD1838D.7030305@suse.cz> Date: Mon, 16 May 2011 16:24:16 -0400 Message-ID: Subject: Re: [PATCH v2] kconfig: autogenerated config_is_xxx macro From: Arnaud Lacombe To: Michal Marek Cc: Valdis.Kletnieks@vt.edu, Jean-Christophe PLAGNIOL-VILLARD , linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, x86@kernel.org, Ingo Molnar 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: 651 Lines: 17 Hi, On Mon, May 16, 2011 at 4:05 PM, Michal Marek wrote: > I figure that this feature is not wanted outside of the kernel build, > though. So what about an option to 'conf' that controls whether these > macros will be generated? > kconfig internal behaviors are mostly controlled by environment variable, which has the advantage to be front-end agnostic, that might be better. - 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/