From: kbuild test robot <lkp@intel.com>
To: Patrick Venture <venture@google.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Olof Johansson <olof@lixom.net>
Subject: drivers/soc/Kconfig:23: 'menu' in different file than 'menu'
Date: Fri, 17 May 2019 12:40:30 +0800 [thread overview]
Message-ID: <201905171226.xchw0NQ2%lkp@intel.com> (raw)
Hi Patrick,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0d74471924f2a01dcd32d154510c0500780b531a
commit: 524feb799408e5d45c6aa82763a9f52489d1e19f soc: add aspeed folder and misc drivers
date: 3 weeks ago
config: xtensa-allyesconfig
compiler: xtensa-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 524feb799408e5d45c6aa82763a9f52489d1e19f
GCC_VERSION=8.1.0 make.cross ARCH=xtensa allyesconfig
GCC_VERSION=8.1.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/soc/Kconfig:23: 'menu' in different file than 'menu'
>> drivers/soc/aspeed/Kconfig:1: location of the 'menu'
>> drivers/Kconfig:233: 'menu' in different file than 'menu'
>> drivers/soc/aspeed/Kconfig:1: location of the 'menu'
<none>:34: syntax error
>> drivers/Kconfig:2: missing end statement for this entry
make[2]: *** [allyesconfig] Error 1
make[1]: *** [allyesconfig] Error 2
make: *** [sub-make] Error 2
--
>> drivers/soc/Kconfig:23: 'menu' in different file than 'menu'
>> drivers/soc/aspeed/Kconfig:1: location of the 'menu'
>> drivers/Kconfig:233: 'menu' in different file than 'menu'
>> drivers/soc/aspeed/Kconfig:1: location of the 'menu'
<none>:34: syntax error
>> drivers/Kconfig:2: missing end statement for this entry
make[2]: *** [oldconfig] Error 1
make[1]: *** [oldconfig] Error 2
make: *** [sub-make] Error 2
--
>> drivers/soc/Kconfig:23: 'menu' in different file than 'menu'
>> drivers/soc/aspeed/Kconfig:1: location of the 'menu'
>> drivers/Kconfig:233: 'menu' in different file than 'menu'
>> drivers/soc/aspeed/Kconfig:1: location of the 'menu'
<none>:34: syntax error
>> drivers/Kconfig:2: missing end statement for this entry
make[2]: *** [olddefconfig] Error 1
make[1]: *** [olddefconfig] Error 2
make: *** [sub-make] Error 2
vim +23 drivers/soc/Kconfig
5d144e36 Andy Gross 2014-04-24 22
3a6e0821 Santosh Shilimkar 2014-04-23 @23 endmenu
:::::: The code at line 23 was first introduced by commit
:::::: 3a6e08218f36baa9c49282ad2fe0dfbf001d8f23 soc: Introduce drivers/soc place-holder for SOC specific drivers
:::::: TO: Santosh Shilimkar <santosh.shilimkar@ti.com>
:::::: CC: Kumar Gala <galak@codeaurora.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-05-17 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 4:40 kbuild test robot [this message]
2019-05-19 2:40 ` Randy Dunlap
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=201905171226.xchw0NQ2%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=venture@google.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
all inboxes | Powered by JetHome®