From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Josh Triplett <josh@joshtriplett.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Michal Marek <mmarek@suse.cz>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Olsa <jolsa@kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] tools/Makefile: Fix Many Many problems and inconsistencies
Date: Tue, 2 Aug 2016 10:41:09 +0200 [thread overview]
Message-ID: <20160802084109.GC13682@piout.net> (raw)
In-Reply-To: <20160802050232.nzgtuijqw46qopyr@x>
On 01/08/2016 at 22:02:33 -0700, Josh Triplett wrote :
> A higher-level item that I think would make a good topic: extracting
> Kconfig into a library usable outside the kernel. Several other
> projects use a copied and hacked-up version of Kconfig. I'd love to see
> it more widely used as a build-time configuration system for more
> projects, but not by forking it out of the kernel each time. I've heard
> kbuild/kconfig maintainers mention that they're interested in seeing
> this done, but don't have the bandwidth to do it.
>
> The thing that makes this a topic, rather than just a thing someone
> needs to just do and submit a patch for, is determining the necessary
> requirements from both the kernel and other projects, so that Kconfig
> doesn't depend on the kernel but that the kernel build system doesn't
> get any more complex to support that.
Well, what about http://ymorin.is-a-geek.org/projects/kconfig-frontends
by the Kconfig maintainer?
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-02 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 3:46 Randy Dunlap
2016-08-02 4:53 ` Wangnan (F)
2016-08-03 19:00 ` Arnaldo Carvalho de Melo
2016-08-02 5:02 ` Josh Triplett
2016-08-02 7:31 ` Arnd Bergmann
2016-08-02 8:27 ` Josh Triplett
2016-08-02 8:41 ` Alexandre Belloni [this message]
2016-08-02 8:43 ` Josh Triplett
2016-09-04 21:15 ` Ben Hutchings
2016-09-06 14:57 ` Arnaldo Carvalho de Melo
2016-09-08 3:25 ` Bamvor Zhang Jian
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=20160802084109.GC13682@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=arjan@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=torvalds@linux-foundation.org \
--cc=yann.morin.1998@free.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox