From: Christoph Hellwig <hch@lst.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Richard Weinberger <richard@nod.at>,
linux-kbuild@vger.kernel.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/9] um: stop abusing KBUILD_KCONFIG
Date: Sun, 8 Jul 2018 08:19:56 -0700 [thread overview]
Message-ID: <20180708152004.21679-2-hch@lst.de> (raw)
In-Reply-To: <20180708152004.21679-1-hch@lst.de>
Instead create a arch/um/Kconfig file that just includes the actual
per-arch Kconfig file.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
arch/um/Kconfig | 3 +++
arch/um/Makefile | 2 --
arch/x86/um/Kconfig | 5 -----
3 files changed, 3 insertions(+), 7 deletions(-)
create mode 100644 arch/um/Kconfig
diff --git a/arch/um/Kconfig b/arch/um/Kconfig
new file mode 100644
index 000000000000..24607af202dc
--- /dev/null
+++ b/arch/um/Kconfig
@@ -0,0 +1,3 @@
+# SPDX-License-Identifier: GPL-2.0
+
+source "arch/$(SUBARCH)/um/Kconfig"
diff --git a/arch/um/Makefile b/arch/um/Makefile
index e54dda8a0363..0207f6316d71 100644
--- a/arch/um/Makefile
+++ b/arch/um/Makefile
@@ -113,8 +113,6 @@ define archhelp
echo ' find in the kernel root.'
endef
-KBUILD_KCONFIG := $(HOST_DIR)/um/Kconfig
-
archheaders:
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.asm-generic \
kbuild-file=$(HOST_DIR)/include/asm/Kbuild \
diff --git a/arch/x86/um/Kconfig b/arch/x86/um/Kconfig
index 9d529f22fd9d..7e509c83d80d 100644
--- a/arch/x86/um/Kconfig
+++ b/arch/x86/um/Kconfig
@@ -1,9 +1,4 @@
# SPDX-License-Identifier: GPL-2.0
-mainmenu "User Mode Linux/$(SUBARCH) $(KERNELVERSION) Kernel Configuration"
-
-comment "Compiler: $(CC_VERSION_TEXT)"
-
-source "scripts/Kconfig.include"
source "arch/um/Kconfig.common"
--
2.18.0
next prev parent reply other threads:[~2018-07-08 15:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 15:19 include architecture Kconfig files from top-level Kconfig v2 Christoph Hellwig
2018-07-08 15:19 ` Christoph Hellwig [this message]
2018-07-08 15:19 ` [PATCH 2/9] um: cleanup Kconfig files Christoph Hellwig
2018-07-08 15:19 ` [PATCH 3/9] um: create a proper drivers Kconfig Christoph Hellwig
2018-07-08 15:19 ` [PATCH 4/9] kconfig: include common Kconfig files from top-level Kconfig Christoph Hellwig
2018-07-11 12:21 ` Masahiro Yamada
2018-07-17 6:33 ` Randy Dunlap
2018-07-17 6:42 ` Randy Dunlap
2018-07-17 6:44 ` Randy Dunlap
2018-07-17 6:55 ` Randy Dunlap
2018-07-17 13:00 ` Christoph Hellwig
2018-07-17 12:59 ` Christoph Hellwig
2018-07-18 7:06 ` Randy Dunlap
2018-07-19 13:11 ` Christoph Hellwig
2018-07-20 19:57 ` Dirk Gouders
2018-07-08 15:20 ` [PATCH 5/9] Kconfig: consolidate the "Kernel hacking" menu Christoph Hellwig
2018-07-08 16:34 ` Randy Dunlap
2018-07-08 15:20 ` [PATCH 6/9] kconfig: include kernel/Kconfig.preempt from init/Kconfig Christoph Hellwig
2018-07-08 16:30 ` Randy Dunlap
2018-07-08 15:20 ` [PATCH 7/9] arch/Kconfig: use a menu to reduce clutter Christoph Hellwig
2018-07-08 15:20 ` [PATCH 8/9] kconfig: move the "Executable file formats" menu to fs/Kconfig.binfmt Christoph Hellwig
2018-07-08 15:20 ` [PATCH 9/9] kconfig: add a Memory Management options" menu Christoph Hellwig
2018-07-23 10:46 ` include architecture Kconfig files from top-level Kconfig v2 Richard Weinberger
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=20180708152004.21679-2-hch@lst.de \
--to=hch@lst.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--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