public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: John Stultz <john.stultz@linaro.org>
Cc: kbuild-all@01.org, lkml <linux-kernel@vger.kernel.org>,
	John Stultz <john.stultz@linaro.org>,
	Laura Abbott <labbott@redhat.com>,
	Benjamin Gaignard <benjamin.gaignard@linaro.org>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	Liam Mark <lmark@codeaurora.org>,
	Pratik Patel <pratikp@codeaurora.org>,
	Brian Starkey <Brian.Starkey@arm.com>,
	Vincent Donnefort <Vincent.Donnefort@arm.com>,
	Sudipto Paul <Sudipto.Paul@arm.com>,
	"Andrew F . Davis" <afd@ti.com>,
	Christoph Hellwig <hch@infradead.org>,
	Chenbo Feng <fengc@google.com>,
	Alistair Strachan <astrachan@google.com>,
	Hridya Valsaraju <hridya@google.com>,
	Hillf Danton <hdanton@sina.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v9 2/5] dma-buf: heaps: Add heap helpers
Date: Thu, 3 Oct 2019 06:09:59 +0800	[thread overview]
Message-ID: <201910030658.lcYVTiTL%lkp@intel.com> (raw)
In-Reply-To: <20191002182255.21808-3-john.stultz@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 2886 bytes --]

Hi John,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[cannot apply to v5.4-rc1 next-20191002]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/John-Stultz/DMA-BUF-Heaps-destaging-ION/20191003-042849
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=mips 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/dma-buf/heaps/heap-helpers.c: In function 'dma_heap_map_kernel':
>> drivers/dma-buf/heaps/heap-helpers.c:43:10: error: implicit declaration of function 'vmap'; did you mean 'bmap'? [-Werror=implicit-function-declaration]
     vaddr = vmap(buffer->pages, buffer->pagecount, VM_MAP, PAGE_KERNEL);
             ^~~~
             bmap
>> drivers/dma-buf/heaps/heap-helpers.c:43:49: error: 'VM_MAP' undeclared (first use in this function); did you mean 'VM_MPX'?
     vaddr = vmap(buffer->pages, buffer->pagecount, VM_MAP, PAGE_KERNEL);
                                                    ^~~~~~
                                                    VM_MPX
   drivers/dma-buf/heaps/heap-helpers.c:43:49: note: each undeclared identifier is reported only once for each function it appears in
   drivers/dma-buf/heaps/heap-helpers.c: In function 'dma_heap_buffer_destroy':
>> drivers/dma-buf/heaps/heap-helpers.c:54:3: error: implicit declaration of function 'vunmap'; did you mean 'kunmap'? [-Werror=implicit-function-declaration]
      vunmap(buffer->vaddr);
      ^~~~~~
      kunmap
   cc1: some warnings being treated as errors

vim +43 drivers/dma-buf/heaps/heap-helpers.c

    38	
    39	static void *dma_heap_map_kernel(struct heap_helper_buffer *buffer)
    40	{
    41		void *vaddr;
    42	
  > 43		vaddr = vmap(buffer->pages, buffer->pagecount, VM_MAP, PAGE_KERNEL);
    44		if (!vaddr)
    45			return ERR_PTR(-ENOMEM);
    46	
    47		return vaddr;
    48	}
    49	
    50	static void dma_heap_buffer_destroy(struct heap_helper_buffer *buffer)
    51	{
    52		if (buffer->vmap_cnt > 0) {
    53			WARN("%s: buffer still mapped in the kernel\n", __func__);
  > 54			vunmap(buffer->vaddr);
    55		}
    56	
    57		buffer->free(buffer);
    58	}
    59	

---
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: 62117 bytes --]

  reply	other threads:[~2019-10-02 22:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 18:22 [PATCH v9 0/5] DMA-BUF Heaps (destaging ION) John Stultz
2019-10-02 18:22 ` [PATCH v9 1/5] dma-buf: Add dma-buf heaps framework John Stultz
2019-10-02 18:22 ` [PATCH v9 2/5] dma-buf: heaps: Add heap helpers John Stultz
2019-10-02 22:09   ` kbuild test robot [this message]
2019-10-02 22:27     ` John Stultz
2019-10-02 22:17   ` kbuild test robot
2019-10-02 18:22 ` [PATCH v9 3/5] dma-buf: heaps: Add system heap to dmabuf heaps John Stultz
2019-10-02 18:22 ` [PATCH v9 4/5] dma-buf: heaps: Add CMA " John Stultz
2019-10-02 18:22 ` [PATCH v9 5/5] kselftests: Add dma-heap test John Stultz
2019-10-03  8:39 ` [PATCH v9 0/5] DMA-BUF Heaps (destaging ION) Brian Starkey

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=201910030658.lcYVTiTL%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Brian.Starkey@arm.com \
    --cc=Sudipto.Paul@arm.com \
    --cc=Vincent.Donnefort@arm.com \
    --cc=afd@ti.com \
    --cc=astrachan@google.com \
    --cc=benjamin.gaignard@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fengc@google.com \
    --cc=hch@infradead.org \
    --cc=hdanton@sina.com \
    --cc=hridya@google.com \
    --cc=john.stultz@linaro.org \
    --cc=kbuild-all@01.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmark@codeaurora.org \
    --cc=pratikp@codeaurora.org \
    --cc=sumit.semwal@linaro.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