[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82c978b2-e9c4-e178-e4b7-621729c2cee4@metux.net>
Date: Thu, 7 Mar 2019 01:10:13 +0100
From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>, Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy@...radead.org>,
Linus Walleij <linusw@...nel.org>,
Enrico Weigelt <info@...ux.net>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH 2/3] x86: apuv2: fix input dependencies
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@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists