Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp1438759imm; Thu, 4 Oct 2018 13:42:26 -0700 (PDT) X-Google-Smtp-Source: ACcGV608+CVjRStVIuUp+CxHRepzT2rg+ReSrbGtdXiIbrAyajbRWoNh2ijgSNF5E1VoQWAxJIGl X-Received: by 2002:a63:ce56:: with SMTP id r22-v6mr7157313pgi.217.1538685746559; Thu, 04 Oct 2018 13:42:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538685746; cv=none; d=google.com; s=arc-20160816; b=IRvOEq+0RS5PdM2W5fLwsJVAUMtQmSxHcChV6CIuc+ir3UAGw6ZtXS1qio7pfODOaO B+OPCJLgWrDJUA+daqSDGeD+xrmWymiA/84oGPlvSij+ZUofTU7bCSdBcLOeVtKbtC/a llgpUnP40La6WfK/SSS3o0chM10jnPFMDh5pekEv9YOT+GcKh3Elt6alhMe4uSEGy4P7 gSamgGDG2HpOoqXlkK4a8wL5prCXFo6N8FTIBcFMokQ5zTiFZqM+ax+4w/Hn5P1ng6HK 1qBZwQ/zKAKmqtqPl7pTP+MsosuY56EvIs1txs5DUJgxC456SP/tFILqkHH1BTrtubs3 W1HQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=8zPlNayqV0Q2cEPpLoWWD7cai0jP8+Gt1FgMdMejGyA=; b=bBxX56yE26Z35Kblts+GfK73nvPRFKsrarYd4277GdTGI3iighJMrDyha3OCbFSumq kJXjRCDdOZ35CSK9EKuFpGEkBa+m+mEuNTbE9I8AsYrbMAz9dWSgnsT0FqnAa/pYu02+ T4GxEImrJiqbdhKKgXUSE7vSOk5q5ydfGJskbSfiJlrhxjHHf602kqprH0tws02wIVGx bz0adJB7lR2v+6GMvFNAIvmPbmsboKqf+RgIlw2X+EzyP4wIoGYxgwxFcpp+su9UBnQ9 J0YTlmD/ASYitpJ+MvpRICqLIXAYPZxv8gUVQnZ9FHwYaLjh8+3T7GMX29z2HZgqLU1C mgag== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j24-v6si5403259pff.42.2018.10.04.13.42.10; Thu, 04 Oct 2018 13:42:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727739AbeJEDg1 (ORCPT + 99 others); Thu, 4 Oct 2018 23:36:27 -0400 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:58459 "EHLO relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727526AbeJEDg0 (ORCPT ); Thu, 4 Oct 2018 23:36:26 -0400 X-Originating-IP: 134.134.139.83 Received: from localhost (unknown [134.134.139.83]) (Authenticated sender: josh@joshtriplett.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 73B59E0002; Thu, 4 Oct 2018 20:41:21 +0000 (UTC) Date: Thu, 4 Oct 2018 13:41:18 -0700 From: Josh Triplett To: Luis Chamberlain Cc: LKML , linux-kbuild@vger.kernel.org, Masahiro Yamada , Randy Dunlap , Sam Ravnborg , Petr Vorel , Steven Rostedt , Johannes Berg , Valentin Rothberg , Vegard Nossum , Felix Fietkau , kconfig-sat@googlegroups.com Subject: Re: [kconfig-sat] [ANN] init-kconfig - easy way to embrace Linux's kconfig Message-ID: <20181004204117.GA10640@localhost> References: <20181004200249.GL5238@garbanzo.do-not-panic.com> <20181004200859.GA10237@localhost> <20181004203950.GN5238@garbanzo.do-not-panic.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181004203950.GN5238@garbanzo.do-not-panic.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 04, 2018 at 01:39:50PM -0700, Luis Chamberlain wrote: > On Thu, Oct 04, 2018 at 01:09:00PM -0700, Josh Triplett wrote: > > On Thu, Oct 04, 2018 at 01:02:49PM -0700, Luis Chamberlain wrote: > > > Every now and then a project is born, and they decide to use Linux's > > > kconfig to enable configuration of their project. As it stands we *know* > > > kconfig is now used in at least over 12 different projects [0]. I myself > > > added kconfig to one as well years ago. Even research reveals that > > > kconfig has become one of the leading industrial variability modeling > > > languages [1] [2]. > > > > > > What is often difficult to do though is to start off using kconfig and > > > integrating it into a project. Or updating / syncing to the latest > > > kconfig from upstream Linux. > > > > > > I had yet another need to use kconfig for another small project so > > > decided to make a clean template others can use and help keep it in sync. > > > This is a passive fork which aims to keep in sync with the Linux > > > kernel's latest kconfig to make it easier to keep up to date and to > > > enable new projects to use and embrace kconfig on their own. The goal > > > is *not* to fork kconfig and evolve it separately, but rather keep in > > > sync with the evolution of kconfig on Linux to make it easier for > > > projects to use kconfig and also update their own kconfig when needed. > > > > Is there a *fundamental* reason that we couldn't have this *be* Linux > > kconfig, whether pulled in by submodule or regular merges, and avoid > > having any divergence at all? > > The structure of kconfig in Linux would have to be changed to make > adoption and sync easier. If that is a goal we wish to embrace, I'm > all for it. I would *love* to see Kconfig in Linux evolved to be more easily reused.