From: Arnaud Lacombe <lacombar@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Arnaud Lacombe <lacombar@gmail.com>
Subject: [PATCH 0/4] Kbuild/Kconfig
Date: Tue, 16 Aug 2011 01:34:10 -0400 [thread overview]
Message-ID: <1313472854-14426-1-git-send-email-lacombar@gmail.com> (raw)
Hi Michal,
The following small serie unexpose a few Kconfig variable from Kbuild, and
vice-versa. The idea is that Kbuild is a user of Kconfig, not the other way
around.
In the same time, fix a couple of place where we hardcode the `.config' string.
Comments Welcome !
- Arnaud
Arnaud Lacombe (4):
kbuild: introduce KBUILD_CONFIG; unexpose KCONFIG_CONFIG
kbuild: reduce kbuild invasivity within kconfig
kbuild: do not hardcode .config
kconfig: do not hardcode .config
Makefile | 20 ++++++++++++++------
arch/arm/boot/compressed/Makefile | 2 +-
arch/unicore32/boot/compressed/Makefile | 2 +-
scripts/kconfig/Makefile | 31 ++++++++++++++++---------------
4 files changed, 32 insertions(+), 23 deletions(-)
--
1.7.6.153.g78432
next reply other threads:[~2011-08-16 5:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 5:34 Arnaud Lacombe [this message]
2011-08-16 5:34 ` [PATCH 1/4] kbuild: introduce KBUILD_CONFIG; unexpose KCONFIG_CONFIG Arnaud Lacombe
2011-09-16 12:31 ` Michal Marek
2011-09-16 12:33 ` Michal Marek
2011-08-16 5:34 ` [PATCH 2/4] kbuild: reduce kbuild invasivity within kconfig Arnaud Lacombe
2011-08-16 5:34 ` [PATCH 3/4] kbuild: do not hardcode .config Arnaud Lacombe
2011-08-16 5:34 ` [PATCH 4/4] kconfig: " Arnaud Lacombe
2011-08-22 15:49 ` [PATCH 0/4] Kbuild/Kconfig Arnaud Lacombe
2011-08-30 0:29 ` Arnaud Lacombe
2011-09-06 15:05 ` Arnaud Lacombe
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=1313472854-14426-1-git-send-email-lacombar@gmail.com \
--to=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
Powered by JetHome