Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [1/6] dma-buf: add dynamic DMA-buf handling v13
Date: Wed, 26 Jun 2019 12:41:29 -0000	[thread overview]
Message-ID: <20190626124129.9081.31698@emeril.freedesktop.org> (raw)
In-Reply-To: <20190626122310.1498-1-christian.koenig@amd.com>

== Series Details ==

Series: series starting with [1/6] dma-buf: add dynamic DMA-buf handling v13
URL   : https://patchwork.freedesktop.org/series/62777/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: dma-buf: add dynamic DMA-buf handling v13
Okay!

Commit: drm/ttm: remove the backing store if no placement is given
Okay!

Commit: drm/ttm: use the parent resv for ghost objects v2
Okay!

Commit: drm/amdgpu: use allowed_domains for exported DMA-bufs
Okay!

Commit: drm/amdgpu: add independent DMA-buf export v6
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:89:5: warning: symbol 'amdgpu_gem_prime_mmap' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:333:27: warning: symbol 'amdgpu_gem_prime_res_obj' was not declared. Should it be static?
-O:drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:324:26: warning: symbol 'amdgpu_dmabuf_ops' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:406:16: warning: symbol 'amdgpu_gem_prime_export' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:438:23: warning: symbol 'amdgpu_gem_prime_import_sg_table' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:487:23: warning: symbol 'amdgpu_gem_prime_import' was not declared. Should it be static?
-O:drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:49:17: warning: symbol 'amdgpu_gem_prime_get_sg_table' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:51:6: warning: symbol 'amdgpu_gem_prime_vmap' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:71:6: warning: symbol 'amdgpu_gem_prime_vunmap' was not declared. Should it be static?

Commit: drm/amdgpu: add independent DMA-buf import v7
Okay!

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-06-26 12:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 12:23 [PATCH 1/6] dma-buf: add dynamic DMA-buf handling v13 Christian König
     [not found] ` <20190626122310.1498-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2019-06-26 12:23   ` [PATCH 2/6] drm/ttm: remove the backing store if no placement is given Christian König
2019-06-26 12:23   ` [PATCH 3/6] drm/ttm: use the parent resv for ghost objects v2 Christian König
2019-06-26 12:23   ` [PATCH 4/6] drm/amdgpu: use allowed_domains for exported DMA-bufs Christian König
2019-06-26 12:23 ` [PATCH 5/6] drm/amdgpu: add independent DMA-buf export v6 Christian König
2019-06-26 12:23 ` [PATCH 6/6] drm/amdgpu: add independent DMA-buf import v7 Christian König
2019-06-26 12:29 ` [PATCH 1/6] dma-buf: add dynamic DMA-buf handling v13 Daniel Vetter
     [not found]   ` <20190626122933.GK12905-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-07-16 14:21     ` Christian König
     [not found]       ` <ef70981d-3d52-b339-b3f5-190635969621-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-07-19  8:57         ` Daniel Vetter
2019-07-19  9:14           ` Koenig, Christian
     [not found]             ` <4704d3c5-894d-6ac1-4afb-06c275700bac-5C7GfCeVMHo@public.gmane.org>
2019-07-19  9:31               ` Daniel Vetter
2019-07-19 12:05                 ` Koenig, Christian
     [not found]                   ` <ff12f6e0-f34b-5ea0-72d5-851ef6bb141f-5C7GfCeVMHo@public.gmane.org>
2019-07-19 13:30                     ` Daniel Vetter
2019-06-26 12:40 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] " Patchwork
2019-06-26 12:41 ` Patchwork [this message]
2019-06-26 13:32 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-06-27  7:28   ` Christian König
2019-07-31  8:55     ` Daniel Vetter
2019-08-07 21:19       ` Daniel Vetter
2019-08-08  7:09         ` Koenig, Christian
2019-08-08  7:29           ` Daniel Vetter
2019-08-08 11:05             ` Koenig, Christian
2019-08-08 11:40               ` Daniel Vetter
2019-08-08  7:59           ` Daniel Vetter
2019-07-31  9:12 ` [PATCH 1/6] " Daniel Vetter
     [not found]   ` <20190731091231.GI7444-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-07-31  9:44     ` Christian König
2019-07-31 10:39       ` Daniel Vetter
     [not found]         ` <CAKMK7uGp64yzpuW_QOJds_ZD=4+z9ymZtpwHT+u2zhD95z4Xnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-07-31 11:19           ` Christian König
2019-07-31 12:41             ` Daniel Vetter

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=20190626124129.9081.31698@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=intel-gfx@lists.freedesktop.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