From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>
Subject: mapping.c:undefined reference to `phys_to_dma'
Date: Sun, 29 Nov 2020 11:39:31 +0800 [thread overview]
Message-ID: <202011291130.cFSQiYZa-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3204 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: aae5ab854e38151e69f261dbf0e3b7e396403178
commit: 5ceda74093a5c1c3f42a02b894df031f3bbc9af1 dma-direct: rename and cleanup __phys_to_dma
date: 3 months ago
config: mips-randconfig-r031-20201129 (attached as .config)
compiler: mips64-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=5ceda74093a5c1c3f42a02b894df031f3bbc9af1
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 5ceda74093a5c1c3f42a02b894df031f3bbc9af1
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
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 >>):
mips64-linux-ld: kernel/dma/mapping.o: in function `dma_map_page_attrs':
>> mapping.c:(.text+0x10c): undefined reference to `phys_to_dma'
mips64-linux-ld: kernel/dma/mapping.o: in function `dma_unmap_page_attrs':
mapping.c:(.text+0x23c): undefined reference to `dma_to_phys'
mips64-linux-ld: mapping.c:(.text+0x274): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/mapping.o: in function `dma_sync_single_for_cpu':
mapping.c:(.text+0x3d4): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_get_required_mask':
>> direct.c:(.text+0xe4): undefined reference to `phys_to_dma'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_alloc':
direct.c:(.text+0x210): undefined reference to `dma_to_phys'
>> mips64-linux-ld: direct.c:(.text+0x2d8): undefined reference to `phys_to_dma'
mips64-linux-ld: direct.c:(.text+0x354): undefined reference to `phys_to_dma'
mips64-linux-ld: direct.c:(.text+0x42c): undefined reference to `phys_to_dma'
mips64-linux-ld: direct.c:(.text+0x4d8): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_free':
direct.c:(.text+0x5d8): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_map_sg':
direct.c:(.text+0x764): undefined reference to `phys_to_dma'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_get_sgtable':
direct.c:(.text+0xa00): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_mmap':
direct.c:(.text+0xb10): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_supported':
direct.c:(.text+0xbf8): undefined reference to `phys_to_dma'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_need_sync':
direct.c:(.text+0xc28): undefined reference to `dma_to_phys'
---
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: 27453 bytes --]
next reply other threads:[~2020-11-29 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 3:39 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-29 14:02 mapping.c:undefined reference to `phys_to_dma' 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=202011291130.cFSQiYZa-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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