From: Christoph Hellwig <hch@lst.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild test robot <lkp@intel.com>, Christoph Hellwig <hch@lst.de>,
kbuild-all@01.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [kbuild:kconfig2 1/10] arch/um/Kconfig:3: can't open file "arch/x86_64/um/Kconfig"
Date: Mon, 30 Jul 2018 18:59:25 +0200 [thread overview]
Message-ID: <20180730165925.GA29494@lst.de> (raw)
In-Reply-To: <20180730094241.GA19128@lst.de>
What do you think of the patch below? This reuses the HEADER_ARCH
variable that uml already needs to setup anyway:
diff --git a/arch/um/Kconfig b/arch/um/Kconfig
index dd4b67131105..6b9938919f0b 100644
--- a/arch/um/Kconfig
+++ b/arch/um/Kconfig
@@ -63,7 +63,7 @@ config NR_CPUS
range 1 1
default 1
-source "arch/$(SUBARCH)/um/Kconfig"
+source "arch/$(HEADER_ARCH)/um/Kconfig"
config STATIC_LINK
bool "Force a static link"
diff --git a/arch/um/Makefile b/arch/um/Makefile
index 0207f6316d71..a88b40ee0332 100644
--- a/arch/um/Makefile
+++ b/arch/um/Makefile
@@ -174,4 +174,4 @@ endef
include/generated/user_constants.h: $(HOST_DIR)/um/user-offsets.s
$(call filechk,gen-asm-offsets)
-export SUBARCH USER_CFLAGS CFLAGS_NO_HARDENING OS DEV_NULL_PATH
+export HEADER_ARCH USER_CFLAGS CFLAGS_NO_HARDENING OS DEV_NULL_PATH
prev parent reply other threads:[~2018-07-30 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 7:23 [kbuild:kconfig2 1/10] arch/um/Kconfig:3: can't open file "arch/x86_64/um/Kconfig" kbuild test robot
2018-07-29 2:11 ` Masahiro Yamada
2018-07-30 9:42 ` Christoph Hellwig
2018-07-30 16:59 ` Christoph Hellwig [this message]
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=20180730165925.GA29494@lst.de \
--to=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--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