From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 9583/10474] drivers/gpu/drm/i915/gt/intel_lrc.c:2523:2: error: implicit declaration of function 'i915_gpu_coredump_put'; did you mean 'i915_gpu_coredump_alloc'?
Date: Tue, 21 Jan 2020 16:02:46 +0800 [thread overview]
Message-ID: <202001211643.3AbDASGP%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3665 bytes --]
Hi Chris,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ccf0726b5c8e44469a1b4f264a53a259c59d2944
commit: 748317386afb235e11616098d2c7772e49776b58 [9583/10474] drm/i915/execlists: Offline error capture
config: i386-randconfig-c002-20200121 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
git checkout 748317386afb235e11616098d2c7772e49776b58
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/gt/intel_lrc.c: In function 'execlists_capture_work':
drivers/gpu/drm/i915/gt/intel_lrc.c:2522:25: error: passing argument 1 of 'i915_error_state_store' from incompatible pointer type [-Werror=incompatible-pointer-types]
i915_error_state_store(cap->error);
^~~
In file included from drivers/gpu/drm/i915/i915_drv.h:97:0,
from drivers/gpu/drm/i915/gt/intel_lrc.c:136:
drivers/gpu/drm/i915/i915_gpu_error.h:317:1: note: expected 'struct drm_i915_private *' but argument is of type 'struct i915_gpu_coredump *'
i915_error_state_store(struct drm_i915_private *i915,
^~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/gt/intel_lrc.c:2522:2: error: too few arguments to function 'i915_error_state_store'
i915_error_state_store(cap->error);
^~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/gpu/drm/i915/i915_drv.h:97:0,
from drivers/gpu/drm/i915/gt/intel_lrc.c:136:
drivers/gpu/drm/i915/i915_gpu_error.h:317:1: note: declared here
i915_error_state_store(struct drm_i915_private *i915,
^~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/i915/gt/intel_lrc.c:2523:2: error: implicit declaration of function 'i915_gpu_coredump_put'; did you mean 'i915_gpu_coredump_alloc'? [-Werror=implicit-function-declaration]
i915_gpu_coredump_put(cap->error);
^~~~~~~~~~~~~~~~~~~~~
i915_gpu_coredump_alloc
cc1: all warnings being treated as errors
vim +2523 drivers/gpu/drm/i915/gt/intel_lrc.c
2499
2500 static void execlists_capture_work(struct work_struct *work)
2501 {
2502 struct execlists_capture *cap = container_of(work, typeof(*cap), work);
2503 const gfp_t gfp = GFP_KERNEL | __GFP_RETRY_MAYFAIL | __GFP_NOWARN;
2504 struct intel_engine_cs *engine = cap->rq->engine;
2505 struct intel_gt_coredump *gt = cap->error->gt;
2506 struct intel_engine_capture_vma *vma;
2507
2508 /* Compress all the objects attached to the request, slow! */
2509 vma = intel_engine_coredump_add_request(gt->engine, cap->rq, gfp);
2510 if (vma) {
2511 struct i915_vma_compress *compress =
2512 i915_vma_capture_prepare(gt);
2513
2514 intel_engine_coredump_add_vma(gt->engine, vma, compress);
2515 i915_vma_capture_finish(gt, compress);
2516 }
2517
2518 gt->simulated = gt->engine->simulated;
2519 cap->error->simulated = gt->simulated;
2520
2521 /* Publish the error state, and announce it to the world */
2522 i915_error_state_store(cap->error);
> 2523 i915_gpu_coredump_put(cap->error);
2524
2525 /* Return this request and all that depend upon it for signaling */
2526 execlists_unhold(engine, cap->rq);
2527
2528 kfree(cap);
2529 }
2530
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 36322 bytes --]
reply other threads:[~2020-01-21 8:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202001211643.3AbDASGP%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.