From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 15770/16121] arch/riscv/include/asm/mmio.h:67:undefined reference to `pci_print_aer'
Date: Mon, 30 Oct 2023 22:53:05 +0800 [thread overview]
Message-ID: <202310302206.Pkr5eBDi-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c503e3eec382ac708ee7adf874add37b77c5d312
commit: 9f39bd073634bb8747e87332aa510172c5f3701c [15770/16121] Merge branch 'for-6.7/cxl-qtg' into cxl/next
config: riscv-randconfig-r002-20220124 (https://download.01.org/0day-ci/archive/20231030/202310302206.Pkr5eBDi-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231030/202310302206.Pkr5eBDi-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/202310302206.Pkr5eBDi-lkp@intel.com/
All errors (new ones prefixed by >>):
riscv64-linux-ld: drivers/cxl/core/pci.o: in function `.L0 ':
>> arch/riscv/include/asm/mmio.h:67:(.text+0xd66): undefined reference to `pci_print_aer'
riscv64-linux-ld: drivers/cxl/core/pci.o: in function `.L0 ':
drivers/cxl/core/pci.c:711:(.text+0xd9a): undefined reference to `pci_print_aer'
riscv64-linux-ld: drivers/cxl/core/pci.o: in function `.LVL326':
drivers/cxl/core/pci.c:753:(.text+0xde4): undefined reference to `pci_print_aer'
vim +67 arch/riscv/include/asm/mmio.h
0c3ac28931d578 Paul Walmsley 2019-10-28 61
0c3ac28931d578 Paul Walmsley 2019-10-28 62 #define __raw_readl __raw_readl
0c3ac28931d578 Paul Walmsley 2019-10-28 63 static inline u32 __raw_readl(const volatile void __iomem *addr)
0c3ac28931d578 Paul Walmsley 2019-10-28 64 {
0c3ac28931d578 Paul Walmsley 2019-10-28 65 u32 val;
0c3ac28931d578 Paul Walmsley 2019-10-28 66
0c3ac28931d578 Paul Walmsley 2019-10-28 @67 asm volatile("lw %0, 0(%1)" : "=r" (val) : "r" (addr));
0c3ac28931d578 Paul Walmsley 2019-10-28 68 return val;
0c3ac28931d578 Paul Walmsley 2019-10-28 69 }
0c3ac28931d578 Paul Walmsley 2019-10-28 70
:::::: The code at line 67 was first introduced by commit
:::::: 0c3ac28931d578324e93afab6ee7b740dfdaff6f riscv: separate MMIO functions into their own header file
:::::: TO: Paul Walmsley <paul.walmsley@sifive.com>
:::::: CC: Paul Walmsley <paul.walmsley@sifive.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-30 14:53 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=202310302206.Pkr5eBDi-lkp@intel.com \
--to=lkp@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--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