From: Felipe Contreras <felipe.contreras@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Linus Torvalds <torvalds@linux-foundation.org>,
Felipe Contreras <felipe.contreras@gmail.com>
Subject: [RFC/PATCH 0/2] A simpler way to maintain custom defconfigs
Date: Thu, 27 Aug 2015 08:08:43 -0500 [thread overview]
Message-ID: <1440680925-2879-1-git-send-email-felipe.contreras@gmail.com> (raw)
Hi,
For several years I've used a trick to be able to maintain a simple defconfig
that works across many versions, and requires little maintenance from my
part:
% cat arch/x86/configs/x86_64_defconfig ~/my-config > .config && make olddefconfig
I'm sending a proposal to integrate it on the build system so that many people
can do the same in a simple manner.
The interesting part is how to generate this simplified defconfig. In a
nutshell; you want to take your .config, remove everything that is the default
in the Kconfig files (what savedefconfig does), but also removes anything that
is in the default defconfig (e.g. x86_64_defconfig)
I've been doing this by hand, but today I gave it a shot to automate this. The
result is a bit crude, but it works.
Thoughts?
Felipe Contreras (2):
kconfig: add KBUILD_USERCONFIG option
kconfig: add KCONFIG_BASECONFIG option to savedefconfig
scripts/kconfig/Makefile | 6 +++
scripts/kconfig/conf.c | 3 ++
scripts/kconfig/confdata.c | 89 +++++++++++++++++++++++++++++++++++++++++++++
scripts/kconfig/lkc_proto.h | 1 +
4 files changed, 99 insertions(+)
--
2.5.0
next reply other threads:[~2015-08-27 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 13:08 Felipe Contreras [this message]
2015-08-27 13:08 ` [RFC/PATCH 1/2] kconfig: add KBUILD_USERCONFIG option Felipe Contreras
2015-08-27 13:08 ` [RFC/PATCH 2/2] kconfig: add KCONFIG_BASECONFIG option to savedefconfig Felipe Contreras
2015-08-28 12:55 ` [RFC/PATCH 0/2] A simpler way to maintain custom defconfigs John Stoffel
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=1440680925-2879-1-git-send-email-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®