From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
linux-arm-kernel@lists.infradead.org
Subject: [arm-platforms:kvm-arm64/mmu/guest-MMIO-guard 20/23] mm/vmalloc.c:2536:13: warning: no previous prototype for function 'iounmap_page_range_hook'
Date: Thu, 1 Jul 2021 08:28:22 +0800 [thread overview]
Message-ID: <202107010814.RbdLflHu-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2603 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git kvm-arm64/mmu/guest-MMIO-guard
head: aadcd7eee6a1082ab94318bcb52fc494cbe0eb47
commit: df21882b06ba969aeede450a4c398a10d18b6aca [20/23] mm/ioremap: Add arch-specific callbacks on ioremap/iounmap calls
config: s390-randconfig-r014-20210630 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 8d21d5472501460933e78aead04cf59579025ba4)
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 s390 cross compiling tool for clang build
# apt-get install binutils-s390x-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/commit/?id=df21882b06ba969aeede450a4c398a10d18b6aca
git remote add arm-platforms https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
git fetch --no-tags arm-platforms kvm-arm64/mmu/guest-MMIO-guard
git checkout df21882b06ba969aeede450a4c398a10d18b6aca
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=s390
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
mm/vmalloc.c:1599:6: warning: no previous prototype for function 'set_iounmap_nonlazy' [-Wmissing-prototypes]
void set_iounmap_nonlazy(void)
^
mm/vmalloc.c:1599:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void set_iounmap_nonlazy(void)
^
static
>> mm/vmalloc.c:2536:13: warning: no previous prototype for function 'iounmap_page_range_hook' [-Wmissing-prototypes]
void __weak iounmap_page_range_hook(phys_addr_t phys_addr, size_t size)
^
mm/vmalloc.c:2536:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void __weak iounmap_page_range_hook(phys_addr_t phys_addr, size_t size)
^
static
mm/vmalloc.c:753:1: warning: unused function 'compute_subtree_max_size' [-Wunused-function]
compute_subtree_max_size(struct vmap_area *va)
^
3 warnings generated.
vim +/iounmap_page_range_hook +2536 mm/vmalloc.c
2535
> 2536 void __weak iounmap_page_range_hook(phys_addr_t phys_addr, size_t size)
2537 {
2538 }
2539
---
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: 15617 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-07-01 0:30 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=202107010814.RbdLflHu-lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.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;
as well as URLs for NNTP newsgroup(s).