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 11:42:41 +0200 [thread overview]
Message-ID: <20180730094241.GA19128@lst.de> (raw)
In-Reply-To: <CAK7LNAS6vY1SMcos_VOaqPUrLUJqgsH9jQ4aKodx5yesCPSCBQ@mail.gmail.com>
On Sun, Jul 29, 2018 at 11:11:47AM +0900, Masahiro Yamada wrote:
> Hi Christoph,
>
> 2018-07-28 16:23 GMT+09:00 kbuild test robot <lkp@intel.com>:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kconfig2
> > head: 0e83fd903bc85173711186755591b61405647cf3
> > commit: 2cc1bfaf2c45056c73970a99c3a7467e157f56aa [1/10] um: stop abusing KBUILD_KCONFIG
> > config: um-x86_64_defconfig
> > compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> > reproduce:
> > git checkout 2cc1bfaf2c45056c73970a99c3a7467e157f56aa
> > make ARCH=um SUBARCH=x86_64 defconfig
> > make ARCH=um SUBARCH=x86_64
>
>
> Hmm.
> SUBARCH is used by arch/x86/um/Kconfig
> to choose 64BIT.
>
> Maybe, do we need $(SUBSRCARCH) ?
>
>
> (In hindsight, HOST_ARCH and HOST_SRCARCH
> might be clearer, though...)
Looks like it. I'll give it a spin and will resend (including the
folded PREEMPT_CODE fix).
next prev parent reply other threads:[~2018-07-30 11:12 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 [this message]
2018-07-30 16:59 ` Christoph Hellwig
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=20180730094241.GA19128@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