From: Patchwork <patchwork@emeril.freedesktop.org>
To: Xidong Wang <wangxidong_97@163.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [1/1] drm/i915:Do not use kfree() to free kmem_cache_alloc() return value
Date: Wed, 04 Apr 2018 12:25:55 -0000 [thread overview]
Message-ID: <20180404122555.12679.88595@emeril.freedesktop.org> (raw)
In-Reply-To: <1522823851-28177-1-git-send-email-wangxidong_97@163.com>
== Series Details ==
Series: series starting with [1/1] drm/i915:Do not use kfree() to free kmem_cache_alloc() return value
URL : https://patchwork.freedesktop.org/series/41137/
State : failure
== Summary ==
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
DESCEND objtool
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/compile.h
CHK kernel/config_data.h
CC [M] drivers/gpu/drm/i915/i915_gem_execbuffer.o
drivers/gpu/drm/i915/i915_gem_execbuffer.c: In function ‘eb_lookup_vmas’:
drivers/gpu/drm/i915/i915_gem_execbuffer.c:731:20: error: passing argument 1 of ‘kmem_cache_free’ from incompatible pointer type [-Werror=incompatible-pointer-types]
kmem_cache_free(lut);
^~~
In file included from ./include/linux/reservation.h:44:0,
from drivers/gpu/drm/i915/i915_gem_execbuffer.c:30:
./include/linux/slab.h:356:6: note: expected ‘struct kmem_cache *’ but argument is of type ‘struct i915_lut_handle *’
void kmem_cache_free(struct kmem_cache *, void *);
^~~~~~~~~~~~~~~
drivers/gpu/drm/i915/i915_gem_execbuffer.c:731:4: error: too few arguments to function ‘kmem_cache_free’
kmem_cache_free(lut);
^~~~~~~~~~~~~~~
In file included from ./include/linux/reservation.h:44:0,
from drivers/gpu/drm/i915/i915_gem_execbuffer.c:30:
./include/linux/slab.h:356:6: note: declared here
void kmem_cache_free(struct kmem_cache *, void *);
^~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
scripts/Makefile.build:324: recipe for target 'drivers/gpu/drm/i915/i915_gem_execbuffer.o' failed
make[4]: *** [drivers/gpu/drm/i915/i915_gem_execbuffer.o] Error 1
scripts/Makefile.build:583: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2
scripts/Makefile.build:583: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:583: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1060: 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:[~2018-04-04 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 6:37 [PATCH 1/1] drm/i915:Do not use kfree() to free kmem_cache_alloc() return value Xidong Wang
2018-04-04 8:16 ` Jani Nikula
2018-04-04 8:16 ` Jani Nikula
2018-04-04 12:25 ` Patchwork [this message]
2018-04-04 13:02 ` kbuild test robot
2018-04-04 13:02 ` kbuild test robot
2018-04-04 13:24 ` kbuild test robot
2018-04-04 13:24 ` kbuild test robot
2018-04-04 13:44 ` kbuild test robot
2018-04-04 13:44 ` kbuild test robot
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=20180404122555.12679.88595@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=wangxidong_97@163.com \
/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.