intel-gfx.lists.freedesktop.org archive mirror
 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/4] dma-buf: change DMA-buf locking convention v2
Date: Mon, 21 Oct 2019 21:50:06 -0000	[thread overview]
Message-ID: <20191021215006.5724.38903@emeril.freedesktop.org> (raw)
In-Reply-To: <20191021111524.14793-1-christian.koenig@amd.com>

== Series Details ==

Series: series starting with [1/4] dma-buf: change DMA-buf locking convention v2
URL   : https://patchwork.freedesktop.org/series/68330/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: dma-buf: change DMA-buf locking convention v2
Okay!

Commit: dma-buf: stop using the dmabuf->lock so much
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

  parent reply	other threads:[~2019-10-21 21:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 11:15 [PATCH 1/4] dma-buf: change DMA-buf locking convention v2 Christian König
2019-10-21 11:15 ` [PATCH 2/4] dma-buf: stop using the dmabuf->lock so much Christian König
2019-10-22 10:13   ` Daniel Vetter
2019-10-21 11:15 ` [PATCH 3/4] drm/amdgpu: add independent DMA-buf export v7 Christian König
2019-10-21 11:15 ` [PATCH 4/4] drm/amdgpu: add independent DMA-buf import v8 Christian König
2019-10-21 21:48 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] dma-buf: change DMA-buf locking convention v2 Patchwork
2019-10-21 21:50 ` Patchwork [this message]
2019-10-21 22:13 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-22  6:46 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-10-22 10:01 ` [PATCH 1/4] " Daniel Vetter
2019-10-22 10:04   ` 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=20191021215006.5724.38903@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;
as well as URLs for NNTP newsgroup(s).