From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-misc:sanitize-vmalloc-api.2 5/32] kernel/dma/remap.c:32:22: error: 'count' undeclared; did you mean 'd_count'?
Date: Tue, 14 Apr 2020 16:22:32 +0800 [thread overview]
Message-ID: <202004141629.y4o7A9ub%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
tree: git://git.infradead.org/users/hch/misc.git sanitize-vmalloc-api.2
head: f44e0a9207268d44a9f106376661ed3c3f764564
commit: eab29baeeab828a08269b7260d4f02462ba99fe3 [5/32] dma-mapping: use vmap insted of reimplementing it
config: xtensa-randconfig-a001-20200414 (attached as .config)
compiler: xtensa-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
git checkout eab29baeeab828a08269b7260d4f02462ba99fe3
# save the attached .config to linux build tree
GCC_VERSION=9.3.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/dma/remap.c: In function 'dma_common_pages_remap':
>> kernel/dma/remap.c:32:22: error: 'count' undeclared (first use in this function); did you mean 'd_count'?
32 | vaddr = vmap(pages, count, VM_DMA_COHERENT, prot);
| ^~~~~
| d_count
kernel/dma/remap.c:32:22: note: each undeclared identifier is reported only once for each function it appears in
vim +32 kernel/dma/remap.c
22
23 /*
24 * Remaps an array of PAGE_SIZE pages into another vm_area.
25 * Cannot be used in non-sleeping contexts
26 */
27 void *dma_common_pages_remap(struct page **pages, size_t size,
28 pgprot_t prot, const void *caller)
29 {
30 void *vaddr;
31
> 32 vaddr = vmap(pages, count, VM_DMA_COHERENT, prot);
33 if (vaddr)
34 find_vm_area(vaddr)->pages = pages;
35 return vaddr;
36 }
37
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30827 bytes --]
reply other threads:[~2020-04-14 8:22 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=202004141629.y4o7A9ub%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.