From: kernel test robot <lkp@intel.com>
To: Alan Kao <alankao@andestech.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: [linux-next:master 10112/13576] arch/Kconfig:10: can't open file "arch/nds32/Kconfig"
Date: Sun, 20 Mar 2022 01:21:44 +0800 [thread overview]
Message-ID: <202203200147.L6cLxtYK-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6d72dda014a4753974eb08950089ddf71fec4f60
commit: aec499c75cf8e0b599be4d559e6922b613085f8f [10112/13576] nds32: Remove the architecture
config: nds32-randconfig-r005-20220319
compiler: nds32le-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=aec499c75cf8e0b599be4d559e6922b613085f8f
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout aec499c75cf8e0b599be4d559e6922b613085f8f
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=nds32 randconfig
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 distclean
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
Makefile:612: arch/nds32/Makefile: No such file or directory
make[1]: *** No rule to make target 'arch/nds32/Makefile'.
make[1]: Failed to remake makefile 'arch/nds32/Makefile'.
>> arch/Kconfig:10: can't open file "arch/nds32/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:77: oldconfig] Error 1
make[1]: *** [Makefile:619: oldconfig] Error 2
make: *** [Makefile:219: __sub-make] Error 2
make: Target 'oldconfig' not remade because of errors.
--
Makefile:612: arch/nds32/Makefile: No such file or directory
make[1]: *** No rule to make target 'arch/nds32/Makefile'.
make[1]: Failed to remake makefile 'arch/nds32/Makefile'.
>> arch/Kconfig:10: can't open file "arch/nds32/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:77: olddefconfig] Error 1
make[1]: *** [Makefile:619: olddefconfig] Error 2
make: *** [Makefile:219: __sub-make] Error 2
make: Target 'olddefconfig' not remade because of errors.
vim +10 arch/Kconfig
125e564582cbce6 Mathieu Desnoyers 2008-02-02 5
1572497cb0e6d20 Christoph Hellwig 2018-07-31 6 #
1572497cb0e6d20 Christoph Hellwig 2018-07-31 7 # Note: arch/$(SRCARCH)/Kconfig needs to be included first so that it can
1572497cb0e6d20 Christoph Hellwig 2018-07-31 8 # override the default values in this file.
1572497cb0e6d20 Christoph Hellwig 2018-07-31 9 #
1572497cb0e6d20 Christoph Hellwig 2018-07-31 @10 source "arch/$(SRCARCH)/Kconfig"
1572497cb0e6d20 Christoph Hellwig 2018-07-31 11
:::::: The code at line 10 was first introduced by commit
:::::: 1572497cb0e6d2016078bc9d5a95786bb878389f kconfig: include common Kconfig files from top-level Kconfig
:::::: TO: Christoph Hellwig <hch@lst.de>
:::::: CC: Masahiro Yamada <yamada.masahiro@socionext.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-03-19 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202203200147.L6cLxtYK-lkp@intel.com \
--to=lkp@intel.com \
--cc=alankao@andestech.com \
--cc=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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