From: Laura Abbott <lauraa@codeaurora.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@01.org
Subject: Re: [next:master 2145/2346] drivers/base/dma-mapping.c:311: undefined reference to `get_vm_area_caller'
Date: Tue, 26 Aug 2014 13:28:26 -0700 [thread overview]
Message-ID: <53FCEDEA.8080105@codeaurora.org> (raw)
In-Reply-To: <53fcfa84.nN6tIZ72fHAO0L0L%fengguang.wu@intel.com>
On 8/26/2014 2:22 PM, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 1c9e4561f3b2afffcda007eae9d0ddd25525f50e
> commit: fa44abcad042144651fa9cd0f698c7c40a59d60f [2145/2346] common: dma-mapping: introduce common remapping functions
> config: make ARCH=microblaze nommu_defconfig
>
> All error/warnings:
>
> drivers/built-in.o: In function `dma_common_pages_remap':
>>> drivers/base/dma-mapping.c:311: undefined reference to `get_vm_area_caller'
>>> drivers/base/dma-mapping.c:315: undefined reference to `map_vm_area'
> drivers/built-in.o: In function `dma_common_free_remap':
>>> drivers/base/dma-mapping.c:328: undefined reference to `find_vm_area'
>
> vim +311 drivers/base/dma-mapping.c
>
> 305 void *dma_common_pages_remap(struct page **pages, size_t size,
> 306 unsigned long vm_flags, pgprot_t prot,
> 307 const void *caller)
> 308 {
> 309 struct vm_struct *area;
> 310
> > 311 area = get_vm_area_caller(size, vm_flags, caller);
> 312 if (!area)
> 313 return NULL;
> 314
> 315 if (map_vm_area(area, prot, pages)) {
> 316 vunmap(area->addr);
> 317 return NULL;
> 318 }
> 319
> 320 return area->addr;
> 321 }
> 322
> 323 /*
> 324 * unmaps a range previously mapped by dma_common_*_remap
> 325 */
> 326 void dma_common_free_remap(void *cpu_addr, size_t size, unsigned long vm_flags)
> 327 {
> 328 struct vm_struct *area = find_vm_area(cpu_addr);
> 329
> 330 if (!area || (area->flags & vm_flags) != vm_flags) {
> 331 WARN(1, "trying to free invalid coherent area: %p\n", cpu_addr);
>
Based on top of my previous patch
----8<------
prev parent reply other threads:[~2014-08-26 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 21:22 [next:master 2145/2346] drivers/base/dma-mapping.c:311: undefined reference to `get_vm_area_caller' kbuild test robot
2014-08-26 20:28 ` Laura Abbott [this message]
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=53FCEDEA.8080105@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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.