linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 81/302] drivers/iommu/intel-iommu.c:3214:3: error: implicit declaration of function 'dma_alloc_from_contiguous'
Date: Fri, 25 Apr 2014 23:17:25 +0800	[thread overview]
Message-ID: <20140425151725.GH31117@localhost> (raw)

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   25153c2ef8124ecd930de79236e7fe25ad2507cb
commit: f57578494f69571fa12bae97cc67884c3522e7c6 [81/302] intel-iommu: integrate DMA CMA
config: make ARCH=ia64 allmodconfig

All error/warnings:

   drivers/iommu/intel-iommu.c: In function 'intel_alloc_coherent':
>> drivers/iommu/intel-iommu.c:3214:3: error: implicit declaration of function 'dma_alloc_from_contiguous' [-Werror=implicit-function-declaration]
>> drivers/iommu/intel-iommu.c:3214:8: warning: assignment makes pointer from integer without a cast [enabled by default]
>> drivers/iommu/intel-iommu.c:3217:4: error: implicit declaration of function 'dma_release_from_contiguous' [-Werror=implicit-function-declaration]
   cc1: some warnings being treated as errors

vim +/dma_alloc_from_contiguous +3214 drivers/iommu/intel-iommu.c

e8bb910d drivers/pci/intel-iommu.c   Alex Williamson       2009-11-04  3208  			flags |= GFP_DMA32;
e8bb910d drivers/pci/intel-iommu.c   Alex Williamson       2009-11-04  3209  	}
ba395927 drivers/pci/intel-iommu.c   Keshavamurthy, Anil S 2007-10-21  3210  
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3211  	if (flags & __GFP_WAIT) {
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3212  		unsigned int count = size >> PAGE_SHIFT;
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3213  
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24 @3214  		page = dma_alloc_from_contiguous(dev, count, order);
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3215  		if (page && iommu_no_mapping(dev) &&
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3216  		    page_to_phys(page) + size > dev->coherent_dma_mask) {
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24 @3217  			dma_release_from_contiguous(dev, page, count);
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3218  			page = NULL;
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3219  		}
f5757849 drivers/iommu/intel-iommu.c Akinobu Mita          2014-04-24  3220  	}

---
0-DAY kernel build testing backend              Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2014-04-25 15:17 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=20140425151725.GH31117@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --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 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).