Kconfig integration was accomplished by integration of Kconfig using
init-kconfig as base. The
way in which we can process the .config file and expand on it for
writing configuration files is inspired by the way in which Kconfig
was embraced in fio-tests.
Since init-kconfig was used
as base it is important to keep track of the fact that the features
of Kconfig from upstream Linux are based on linux-next tag next-20181002.
Fortunately, this linux-next tag already carried kconfig with support for
macro use.