From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Linus Walleij <linusw@kernel.org>,
Enrico Weigelt <info@metux.net>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 2/3] x86: apuv2: fix input dependencies
Date: Thu, 7 Mar 2019 01:10:13 +0100 [thread overview]
Message-ID: <82c978b2-e9c4-e178-e4b7-621729c2cee4@metux.net> (raw)
In-Reply-To: <CAHp75Vcd0eNCBtxb1huMBGFF9JXmropHv2YA1eh-yK3iMFfuFQ@mail.gmail.com>
On 05.03.19 14:56, Andy Shevchenko wrote:
>
> Darren gave a talk about merging kernel configs to get something like
> you want to.
> This tool is quite long already lying around. merge_config.sh in your
> kernel source tree.
Yes, that's similar to how some distros (eg. yocto) do it.
But my requirements are a bit more complex:
In my final meta-config, I just wanna say:
* i have board A (possibly multiple boards)
* i need features X, Y, Z (eg. eth, display, can, ext4, acl, ...)
And that shall be all to generate a minimal config for exactly those
requirements.
Doing that by just putting config snippets together, quickly turns into
a maintenance hell. At least you'd need recursive dependencies and some
if/else logic.
That's why I've written kmct:
https://github.com/metux/kmct
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-03-07 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190304201930.1622839-1-arnd@arndb.de>
[not found] ` <20190304201930.1622839-2-arnd@arndb.de>
[not found] ` <a94c3c6a-481e-96a5-74e1-8c3299c74129@metux.net>
[not found] ` <CAK8P3a0vdhCTNTF-K0mXjRWkPvv0qr3nf_52=8n6zTa7p3ELLw@mail.gmail.com>
2019-03-05 13:50 ` [PATCH 2/3] x86: apuv2: fix input dependencies Enrico Weigelt, metux IT consult
2019-03-05 13:56 ` Andy Shevchenko
2019-03-07 0:10 ` Enrico Weigelt, metux IT consult [this message]
2019-03-07 7:03 ` Darren Hart
2019-03-05 16:46 ` Arnd Bergmann
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=82c978b2-e9c4-e178-e4b7-621729c2cee4@metux.net \
--to=lkml@metux.net \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=arnd@arndb.de \
--cc=dvhart@infradead.org \
--cc=info@metux.net \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox