All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>,
	linux-kbuild@vger.kernel.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Sam Ravnborg <sam@ravnborg.org>, Petr Vorel <pvorel@suse.cz>,
	Steven Rostedt <rostedt@goodmis.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	Vegard Nossum <vegard.nossum@oracle.com>,
	Felix Fietkau <nbd@nbd.name>,
	kconfig-sat@googlegroups.com
Subject: [ANN] init-kconfig - easy way to embrace Linux's kconfig
Date: Thu, 4 Oct 2018 13:02:49 -0700	[thread overview]
Message-ID: <20181004200249.GL5238@garbanzo.do-not-panic.com> (raw)

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.

This may also be useful if folks want to test R&D code on a smaller
compartamentalized codebase.

If you find this useful and you'd like to help keep it in sync, send
patches my way as the kernel's kconfig evolves. The code is up on
gitlab [3].

Do we want to document this option on Linux in case folks want to try
and embrace kconfig on their own for other projects?
  
[0] http://www.eng.uwaterloo.ca/~shshe/kconfig_semantics.pdf
[1] http://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
[2] http://gsd.uwaterloo.ca/sites/default/files/ase241-berger_0.pdf
[3] https://gitlab.com/mcgrof/init-kconfig

  Luis

             reply	other threads:[~2018-10-04 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 20:02 Luis Chamberlain [this message]
2018-10-04 20:09 ` [kconfig-sat] [ANN] init-kconfig - easy way to embrace Linux's kconfig Josh Triplett
2018-10-04 20:39   ` Luis Chamberlain
2018-10-04 20:41     ` Josh Triplett
2018-10-04 20:53       ` Luis Chamberlain
2018-10-04 22:05         ` Steven Rostedt
2018-10-05  0:18 ` Randy Dunlap
2018-10-05 10:48 ` Masahiro Yamada
2018-11-21 22:58   ` [kconfig-sat] " Luis Chamberlain
2018-10-06  5:53 ` Ulf Magnusson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181004200249.GL5238@garbanzo.do-not-panic.com \
    --to=mcgrof@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=kconfig-sat@googlegroups.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@nbd.name \
    --cc=pvorel@suse.cz \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sam@ravnborg.org \
    --cc=valentinrothberg@gmail.com \
    --cc=vegard.nossum@oracle.com \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.