From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10800/10966] arch/arm/include/asm/highmem.h:52:43: error: implicit declaration of function 'cache_is_vivt'
Date: Sun, 6 Dec 2020 04:44:14 +0800 [thread overview]
Message-ID: <202012060411.By0ouRhK-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2731 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2996bd3f6ca9ea529b40c369a94b247657abdb4d
commit: 785037f08e4f6255041131d3575ca13bfe603ddf [10800/10966] Merge remote-tracking branch 'tip/auto-latest'
config: arm-randconfig-r031-20201206 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project fc7818f5d6906555cebad2c2e7c313a383b9cb82)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=785037f08e4f6255041131d3575ca13bfe603ddf
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 785037f08e4f6255041131d3575ca13bfe603ddf
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm
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/arm/mm/kasan_init.c:18:
>> arch/arm/include/asm/highmem.h:52:43: error: implicit declaration of function 'cache_is_vivt' [-Werror,-Wimplicit-function-declaration]
if (IS_ENABLED(CONFIG_DEBUG_HIGHMEM) && !cache_is_vivt())
^
1 error generated.
vim +/cache_is_vivt +52 arch/arm/include/asm/highmem.h
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 49
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 50 static inline void *arch_kmap_local_high_get(struct page *page)
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 51 {
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 @52 if (IS_ENABLED(CONFIG_DEBUG_HIGHMEM) && !cache_is_vivt())
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 53 return NULL;
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 54 return kmap_high_get(page);
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 55 }
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 56 #define arch_kmap_local_high_get arch_kmap_local_high_get
2a15ba82fa6ca3 Thomas Gleixner 2020-11-03 57
:::::: The code at line 52 was first introduced by commit
:::::: 2a15ba82fa6ca3f35502b3060f22118a938d2889 ARM: highmem: Switch to generic kmap atomic
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38523 bytes --]
reply other threads:[~2020-12-05 20:45 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=202012060411.By0ouRhK-lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=tglx@linutronix.de \
/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