From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>, Stafford Horne <shorne@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [openrisc:for-next 3/3] arch/openrisc/include/asm/setup.h:11:13: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'or1k_early_setup'
Date: Fri, 6 Aug 2021 22:46:16 -0700 [thread overview]
Message-ID: <50c8f758-91de-8f0a-57e1-07e71afcdbde@infradead.org> (raw)
In-Reply-To: <202108052040.jEu76XzR-lkp@intel.com>
On 8/5/21 5:04 AM, kernel test robot wrote:
> tree: https://github.com/openrisc/linux.git for-next
> head: 19e14f3a81d227f1c8b8d5371de28b3ab3deb556
> commit: 19e14f3a81d227f1c8b8d5371de28b3ab3deb556 [3/3] openrisc: Fix compiler warnings in setup
> config: openrisc-randconfig-r005-20210804 (attached as .config)
> compiler: or1k-linux-gcc (GCC) 10.3.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://github.com/openrisc/linux/commit/19e14f3a81d227f1c8b8d5371de28b3ab3deb556
> git remote add openrisc https://github.com/openrisc/linux.git
> git fetch --no-tags openrisc for-next
> git checkout 19e14f3a81d227f1c8b8d5371de28b3ab3deb556
> # save the attached .config to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=openrisc SHELL=/bin/bash
>
> 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 >>):
>
> In file included from arch/openrisc/include/asm/page.h:35,
> from drivers/usb/atm/speedtch.c:12:
>>> arch/openrisc/include/asm/setup.h:11:13: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'or1k_early_setup'
> 11 | void __init or1k_early_setup(void *fdt);
> | ^~~~~~~~~~~~~~~~
>
>
> vim +11 arch/openrisc/include/asm/setup.h
Hi Stafford-
#include <linux/init.h>
and where is this file?
#include <asm-generic/setup.h>
> 9
> 10 #ifndef __ASSEMBLY__
> > 11 void __init or1k_early_setup(void *fdt);
> 12 #endif
> 13
>
> ---
--
~Randy
next prev parent reply other threads:[~2021-08-07 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 12:04 kernel test robot
2021-08-07 5:46 ` Randy Dunlap [this message]
2021-08-07 5:51 ` 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=50c8f758-91de-8f0a-57e1-07e71afcdbde@infradead.org \
--to=rdunlap@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=shorne@gmail.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®