From: kernel test robot <lkp@intel.com>
To: Anup Patel <anup@brainfault.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10734/10788] arch/riscv/kvm/aia_imsic.c:237:9: error: call to undeclared function 'arch_atomic_long_fetch_or'; ISO C99 and later do not support implicit function declarations
Date: Mon, 19 Jun 2023 16:43:05 +0800 [thread overview]
Message-ID: <202306191640.NE97q8G3-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 47045630bc409ce6606d97b790895210dd1d517d
commit: 45d0f6cbccb6e26047d42baa32de1df7bbc25f97 [10734/10788] Merge branch 'riscv_kvm_next' of https://github.com/kvm-riscv/linux.git
config: riscv-randconfig-r042-20230619 (https://download.01.org/0day-ci/archive/20230619/202306191640.NE97q8G3-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230619/202306191640.NE97q8G3-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306191640.NE97q8G3-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/riscv/kvm/aia_imsic.c:237:9: error: call to undeclared function 'arch_atomic_long_fetch_or'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
237 | return arch_atomic_long_fetch_or(val, (atomic_long_t *)ptr);
| ^
arch/riscv/kvm/aia_imsic.c:237:9: note: did you mean 'raw_atomic_long_fetch_or'?
include/linux/atomic/atomic-long.h:1087:1: note: 'raw_atomic_long_fetch_or' declared here
1087 | raw_atomic_long_fetch_or(long i, atomic_long_t *v)
| ^
1 error generated.
vim +/arch_atomic_long_fetch_or +237 arch/riscv/kvm/aia_imsic.c
2f68d542041204 Anup Patel 2023-06-15 232
2f68d542041204 Anup Patel 2023-06-15 233 static unsigned long imsic_mrif_atomic_or(struct imsic_mrif *mrif,
2f68d542041204 Anup Patel 2023-06-15 234 unsigned long *ptr,
2f68d542041204 Anup Patel 2023-06-15 235 unsigned long val)
2f68d542041204 Anup Patel 2023-06-15 236 {
2f68d542041204 Anup Patel 2023-06-15 @237 return arch_atomic_long_fetch_or(val, (atomic_long_t *)ptr);
2f68d542041204 Anup Patel 2023-06-15 238 }
2f68d542041204 Anup Patel 2023-06-15 239
:::::: The code at line 237 was first introduced by commit
:::::: 2f68d5420412040ec974557198d6a886708479c0 RISC-V: KVM: Add in-kernel virtualization of AIA IMSIC
:::::: TO: Anup Patel <apatel@ventanamicro.com>
:::::: CC: Anup Patel <anup@brainfault.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-19 8:43 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=202306191640.NE97q8G3-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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