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 `dma_to_phys'
Date: Tue, 29 Dec 2020 15:16:23 +0800 [thread overview]
Message-ID: <202012291515.3rDKSOle-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3438 bytes --]
Hi Christoph,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: dea8dcf2a9fa8cc540136a6cd885c3beece16ec3
commit: 7bc5c428a660d4d1bc95ba54bf4cb6bccf8c3029 dma-direct: remove __dma_to_phys
date: 4 months ago
config: mips-randconfig-s031-20201220 (attached as .config)
compiler: mips64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-184-g1b896707-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7bc5c428a660d4d1bc95ba54bf4cb6bccf8c3029
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 7bc5c428a660d4d1bc95ba54bf4cb6bccf8c3029
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' 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+0x108): undefined reference to `__phys_to_dma'
mips64-linux-ld: kernel/dma/mapping.o: in function `dma_unmap_page_attrs':
>> mapping.c:(.text+0x24c): undefined reference to `dma_to_phys'
>> mips64-linux-ld: mapping.c:(.text+0x28c): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/mapping.o: in function `dma_sync_single_for_cpu':
mapping.c:(.text+0x490): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/mapping.o: in function `dma_sync_single_for_device':
mapping.c:(.text+0x4f0): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_get_required_mask':
direct.c:(.text+0xb4): undefined reference to `__phys_to_dma'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_alloc':
>> direct.c:(.text+0x1dc): undefined reference to `dma_to_phys'
mips64-linux-ld: direct.c:(.text+0x2bc): undefined reference to `__phys_to_dma'
mips64-linux-ld: direct.c:(.text+0x398): undefined reference to `__phys_to_dma'
>> mips64-linux-ld: direct.c:(.text+0x428): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_free':
direct.c:(.text+0x55c): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_map_sg':
direct.c:(.text+0x69c): undefined reference to `__phys_to_dma'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_get_sgtable':
direct.c:(.text+0x8c8): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_mmap':
direct.c:(.text+0x9cc): undefined reference to `dma_to_phys'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_supported':
direct.c:(.text+0xaa8): undefined reference to `__phys_to_dma'
mips64-linux-ld: kernel/dma/direct.o: in function `dma_direct_need_sync':
direct.c:(.text+0xad8): 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: 24944 bytes --]
next reply other threads:[~2020-12-29 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 7:16 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-29 0:25 mapping.c:undefined reference to `dma_to_phys' 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=202012291515.3rDKSOle-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;
as well as URLs for NNTP newsgroup(s).