From: kbuild test robot <lkp@intel.com>
To: vitaly_kuzmichev@mentor.com
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
mark.rutland@arm.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
george_davis@mentor.com, vitaly_kuzmichev@mentor.com
Subject: Re: [PATCH 1/2] drivers: dma-coherent: Add support for default DMA coherent pool
Date: Wed, 5 Jul 2017 05:02:25 +0800 [thread overview]
Message-ID: <201707050435.toRcTTtv%fengguang.wu@intel.com> (raw)
In-Reply-To: <1499093475-29859-2-git-send-email-vitaly_kuzmichev@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
Hi George,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.12]
[cannot apply to next-20170704]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/vitaly_kuzmichev-mentor-com/drivers-dma-coherent-Add-support-for-default-DMA-coherent-pool/20170705-040238
config: i386-randconfig-x075-07041126 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/base/dma-coherent.c: In function 'dev_get_dma_area':
>> drivers/base/dma-coherent.c:28:16: error: 'struct device' has no member named 'cma_area'; did you mean 'dma_parms'?
if (dev && dev->cma_area)
^~
vim +28 drivers/base/dma-coherent.c
22
23 static inline struct dma_coherent_mem *dev_get_dma_area(struct device *dev)
24 {
25 if (dev && dev->dma_mem)
26 return dev->dma_mem;
27 #ifdef CONFIG_CMA
> 28 if (dev && dev->cma_area)
29 return NULL;
30 #endif
31 return dma_coherent_default_area ? *dma_coherent_default_area : NULL;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26083 bytes --]
next prev parent reply other threads:[~2017-07-04 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 14:51 [PATCH 0/2] Implement " vitaly_kuzmichev
2017-07-03 14:51 ` [PATCH 1/2] drivers: dma-coherent: Add support for " vitaly_kuzmichev
2017-07-04 21:02 ` kbuild test robot [this message]
2017-07-05 5:55 ` kbuild test robot
2017-07-10 0:36 ` Rob Herring
2017-07-03 14:51 ` [PATCH 2/2] drivers: dma-coherent: show per-device DMA region utilization via procfs vitaly_kuzmichev
2017-07-07 13:22 ` [PATCH v2 0/2] Additions to default DMA coherent pool Vitaly Kuzmichev
2017-07-07 13:22 ` [PATCH v2 1/2] drivers: dma-coherent: Fix dev->cma_area vs dev->dma_mem breakage Vitaly Kuzmichev
2017-07-07 14:27 ` Christoph Hellwig
2017-07-07 15:40 ` Vladimir Murzin
2017-07-07 16:06 ` Robin Murphy
2017-07-07 16:44 ` Vladimir Murzin
2017-07-07 17:55 ` Robin Murphy
2017-07-10 13:42 ` Vladimir Murzin
2017-07-11 14:19 ` Christoph Hellwig
2017-07-07 13:23 ` [PATCH v2 2/2] drivers: dma-coherent: show per-device DMA region utilization via procfs Vitaly Kuzmichev
2017-07-07 14:28 ` Christoph Hellwig
2017-07-07 13:55 ` [PATCH v2 0/2] Additions to default DMA coherent pool Stephen Rothwell
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=201707050435.toRcTTtv%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=george_davis@mentor.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vitaly_kuzmichev@mentor.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
all inboxes | Powered by JetHome®