From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for dma-buf: Flag vmap'ed memory as system or I/O memory
Date: Mon, 14 Sep 2020 17:41:01 -0000 [thread overview]
Message-ID: <160010526126.5913.11298151789356120445@emeril.freedesktop.org> (raw)
In-Reply-To: <20200914112521.1327-1-tzimmermann@suse.de>
== Series Details ==
Series: dma-buf: Flag vmap'ed memory as system or I/O memory
URL : https://patchwork.freedesktop.org/series/81647/
State : failure
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
CC [M] drivers/gpu/drm/i915/gem/i915_gem_dmabuf.o
In file included from drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c:291:0:
drivers/gpu/drm/i915/gem/selftests/mock_dmabuf.c:89:10: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.vmap = mock_dmabuf_vmap,
^~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/gem/selftests/mock_dmabuf.c:89:10: note: (near initialization for ‘mock_dmabuf_ops.vmap’)
drivers/gpu/drm/i915/gem/selftests/mock_dmabuf.c:90:12: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.vunmap = mock_dmabuf_vunmap,
^~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/gem/selftests/mock_dmabuf.c:90:12: note: (near initialization for ‘mock_dmabuf_ops.vunmap’)
cc1: all warnings being treated as errors
scripts/Makefile.build:283: recipe for target 'drivers/gpu/drm/i915/gem/i915_gem_dmabuf.o' failed
make[4]: *** [drivers/gpu/drm/i915/gem/i915_gem_dmabuf.o] Error 1
scripts/Makefile.build:500: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2
scripts/Makefile.build:500: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:500: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1784: recipe for target 'drivers' failed
make: *** [drivers] Error 2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-09-14 17:41 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 11:25 [PATCH 0/3] dma-buf: Flag vmap'ed memory as system or I/O memory Thomas Zimmermann
2020-09-14 11:25 ` [Intel-gfx] " Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 11:25 ` [PATCH 1/3] dma-buf: Add struct dma-buf-map for storing struct dma_buf.vaddr_ptr Thomas Zimmermann
2020-09-14 11:25 ` [Intel-gfx] " Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 11:25 ` [PATCH 2/3] dma-buf: Use struct dma_buf_map in dma_buf_vmap() interfaces Thomas Zimmermann
2020-09-14 11:25 ` [Intel-gfx] " Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 18:33 ` [Intel-gfx] " kernel test robot
2020-09-14 23:54 ` kernel test robot
2020-09-15 1:56 ` kernel test robot
2020-09-16 9:35 ` Daniel Vetter
2020-09-16 9:35 ` [Intel-gfx] " Daniel Vetter
2020-09-16 9:35 ` Daniel Vetter
2020-09-16 9:35 ` Daniel Vetter
2020-09-14 11:25 ` [PATCH 3/3] dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces Thomas Zimmermann
2020-09-14 11:25 ` [Intel-gfx] " Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 11:25 ` Thomas Zimmermann
2020-09-14 17:22 ` [Intel-gfx] " kernel test robot
2020-09-14 19:28 ` kernel test robot
2020-09-14 17:41 ` Patchwork [this message]
2020-09-16 9:37 ` [PATCH 0/3] dma-buf: Flag vmap'ed memory as system or I/O memory Daniel Vetter
2020-09-16 9:37 ` [Intel-gfx] " Daniel Vetter
2020-09-16 9:37 ` Daniel Vetter
2020-09-16 9:37 ` Daniel Vetter
2020-09-16 10:48 ` Thomas Zimmermann
2020-09-16 10:48 ` [Intel-gfx] " Thomas Zimmermann
2020-09-16 10:48 ` Thomas Zimmermann
2020-09-16 10:48 ` Thomas Zimmermann
2020-09-16 12:24 ` Daniel Vetter
2020-09-16 12:24 ` [Intel-gfx] " Daniel Vetter
2020-09-16 12:24 ` Daniel Vetter
2020-09-16 12:24 ` Daniel Vetter
2020-09-16 12:59 ` Christian König
2020-09-16 12:59 ` [Intel-gfx] " Christian König
2020-09-16 12:59 ` Christian König
2020-09-16 12:59 ` Christian König
2020-09-16 13:12 ` Thomas Zimmermann
2020-09-16 13:12 ` [Intel-gfx] " Thomas Zimmermann
2020-09-16 13:12 ` Thomas Zimmermann
2020-09-16 13:12 ` Thomas Zimmermann
2020-09-16 13:37 ` Thomas Hellström (Intel)
2020-09-17 7:16 ` Thomas Zimmermann
2020-09-17 8:04 ` Christian König
2020-09-18 6:06 ` Sumit Semwal
2020-09-18 6:18 ` Sumit Semwal
2020-09-18 6:06 ` [Intel-gfx] " Sumit Semwal
2020-09-18 6:06 ` Sumit Semwal
2020-09-18 8:32 ` Sumit Semwal
2020-09-18 8:44 ` Sumit Semwal
2020-09-18 8:32 ` [Intel-gfx] " Sumit Semwal
2020-09-18 8:32 ` Sumit Semwal
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=160010526126.5913.11298151789356120445@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.