From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>, Guo Ren <guoren@linux.alibaba.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: arch/csky/mm/tcm.c:14:2: error: #error "You should define DTCM_RAM_BASE"
Date: Fri, 14 May 2021 16:22:01 -0700 [thread overview]
Message-ID: <a386406d-40fd-d382-b272-e524f046ca71@infradead.org> (raw)
In-Reply-To: <202105150718.cdDLUzFD-lkp@intel.com>
On 5/14/21 4:08 PM, kernel test robot wrote:
> Hi Guo,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 25a1298726e97b9d25379986f5d54d9e62ad6e93
> commit: 18c07d23da5a48525b2955aa269b8bb108c19300 csky: Fixup calltrace panic
> date: 1 year ago
> config: csky-randconfig-r036-20210515 (attached as .config)
> compiler: csky-linux-gcc (GCC) 9.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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=18c07d23da5a48525b2955aa269b8bb108c19300
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 18c07d23da5a48525b2955aa269b8bb108c19300
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=csky
>
> 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 >>):
>
>>> arch/csky/mm/tcm.c:14:2: error: #error "You should define DTCM_RAM_BASE"
> 14 | #error "You should define DTCM_RAM_BASE"
> | ^~~~~
> arch/csky/mm/tcm.c:109:7: warning: no previous prototype for 'tcm_alloc' [-Wmissing-prototypes]
> 109 | void *tcm_alloc(size_t len)
> | ^~~~~~~~~
> arch/csky/mm/tcm.c:124:6: warning: no previous prototype for 'tcm_free' [-Wmissing-prototypes]
> 124 | void tcm_free(void *addr, size_t len)
> | ^~~~~~~~
>
>
> vim +14 arch/csky/mm/tcm.c
>
> f525bb2c9e7cf1 Guo Ren 2019-11-27 11
> f525bb2c9e7cf1 Guo Ren 2019-11-27 12 #ifdef CONFIG_HAVE_DTCM
> f525bb2c9e7cf1 Guo Ren 2019-11-27 13 #if (CONFIG_DTCM_RAM_BASE == 0xffffffff)
> f525bb2c9e7cf1 Guo Ren 2019-11-27 @14 #error "You should define DTCM_RAM_BASE"
> f525bb2c9e7cf1 Guo Ren 2019-11-27 15 #endif
> f525bb2c9e7cf1 Guo Ren 2019-11-27 16
I.e., the person or bot that is running the kernel configurator should
set/define the Kconfig symbol CONFIG_DTCM_RAM_BASE.
Please do so in your scripts.
Thanks.
> :::::: The code at line 14 was first introduced by commit
> :::::: f525bb2c9e7cf1e3c43ab57704c9e1c836d30b34 csky: Tightly-Coupled Memory or Sram support
>
> :::::: TO: Guo Ren <guoren@linux.alibaba.com>
> :::::: CC: Guo Ren <guoren@linux.alibaba.com>
--
~Randy
next prev parent reply other threads:[~2021-05-14 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 23:08 kernel test robot
2021-05-14 23:22 ` Randy Dunlap [this message]
2021-05-18 11:48 ` [kbuild-all] " Chen, Rong A
-- strict thread matches above, loose matches on Subject: below --
2021-03-04 15:43 kernel test robot
2021-02-04 9:48 kernel test robot
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=a386406d-40fd-d382-b272-e524f046ca71@infradead.org \
--to=rdunlap@infradead.org \
--cc=guoren@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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®