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/4] dma-buf: change DMA-buf locking convention
Date: Thu, 29 Aug 2019 16:43:29 -0000 [thread overview]
Message-ID: <20190829164329.10003.60023@emeril.freedesktop.org> (raw)
In-Reply-To: <20190829142917.13058-1-christian.koenig@amd.com>
== Series Details ==
Series: series starting with [1/4] dma-buf: change DMA-buf locking convention
URL : https://patchwork.freedesktop.org/series/66006/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: dma-buf: change DMA-buf locking convention
Okay!
Commit: drm/ttm: use the parent resv for ghost objects v2
Okay!
Commit: drm/amdgpu: add independent DMA-buf export v7
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:353:16: warning: symbol 'amdgpu_gem_prime_export' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:385: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:434:23: warning: symbol 'amdgpu_gem_prime_import' 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?
-drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:89:5: warning: symbol 'amdgpu_gem_prime_mmap' was not declared. Should it be static?
-O:drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c:310:26: warning: symbol 'amdgpu_dmabuf_ops' 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?
Commit: drm/amdgpu: add independent DMA-buf import v8
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-29 16:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 14:29 Dynamic DMA-buf locking changes Christian König
2019-08-29 14:29 ` [PATCH 1/4] dma-buf: change DMA-buf locking convention Christian König
2019-09-03 8:05 ` Daniel Vetter
2019-09-11 10:53 ` Christian König
2019-09-16 12:23 ` Christian König
2019-09-17 12:31 ` Daniel Vetter
2019-09-17 12:40 ` Koenig, Christian
2019-09-17 13:13 ` Daniel Vetter
2019-09-17 13:24 ` Koenig, Christian
2019-09-17 13:45 ` Daniel Vetter
2019-09-17 14:47 ` Koenig, Christian
2019-09-17 14:56 ` Daniel Vetter
2019-09-24 9:51 ` Koenig, Christian
2019-10-02 8:37 ` Koenig, Christian
2019-10-08 8:55 ` Daniel Vetter
2019-10-16 13:46 ` Koenig, Christian
2019-10-16 14:23 ` Daniel Vetter
2019-10-17 9:04 ` Koenig, Christian
2019-10-08 8:55 ` Daniel Vetter
2019-08-29 14:29 ` [PATCH 2/4] drm/ttm: use the parent resv for ghost objects v2 Christian König
2019-10-08 9:25 ` Daniel Vetter
2019-10-09 13:10 ` Christian König
2019-10-09 14:09 ` Daniel Vetter
2019-08-29 14:29 ` [PATCH 3/4] drm/amdgpu: add independent DMA-buf export v7 Christian König
2019-08-29 14:29 ` [PATCH 4/4] drm/amdgpu: add independent DMA-buf import v8 Christian König
2019-08-29 16:42 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] dma-buf: change DMA-buf locking convention Patchwork
2019-08-29 16:43 ` Patchwork [this message]
2019-08-29 17:05 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-30 7:18 ` ✓ Fi.CI.IGT: " Patchwork
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=20190829164329.10003.60023@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