Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915/execlists: Always reset the context's RING registers (rev4)
Date: Mon, 08 Apr 2019 20:38:44 -0000	[thread overview]
Message-ID: <20190408203844.21094.32888@emeril.freedesktop.org> (raw)
In-Reply-To: <20190408131506.1180-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915/execlists: Always reset the context's RING registers (rev4)
URL   : https://patchwork.freedesktop.org/series/59174/
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/header_test_i915_active_types.o
  CC [M]  drivers/gpu/drm/i915/header_test_i915_gem_context_types.o
  CC [M]  drivers/gpu/drm/i915/header_test_i915_priolist_types.o
  CC [M]  drivers/gpu/drm/i915/header_test_i915_scheduler_types.o
  CC [M]  drivers/gpu/drm/i915/header_test_i915_timeline_types.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_atomic_plane.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_audio.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_cdclk.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_color.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_connector.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_context_types.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_crt.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_csr.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_ddi.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_dp.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_dvo.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_engine_types.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_fbc.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_fbdev.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_frontbuffer.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_hdcp.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_hdmi.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_lspcon.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_lvds.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_panel.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_pipe_crc.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_pm.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_psr.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_sdvo.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_sprite.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_tv.o
  CC [M]  drivers/gpu/drm/i915/header_test_intel_workarounds_types.o
  CC [M]  drivers/gpu/drm/i915/intel_lrc.o
drivers/gpu/drm/i915/intel_lrc.c: In function ‘execlists_cancel_requests’:
drivers/gpu/drm/i915/intel_lrc.c:946:2: error: implicit declaration of function ‘process_csb’ [-Werror=implicit-function-declaration]
  process_csb(engine);
  ^~~~~~~~~~~
drivers/gpu/drm/i915/intel_lrc.c: At top level:
drivers/gpu/drm/i915/intel_lrc.c:994:13: error: conflicting types for ‘process_csb’ [-Werror]
 static void process_csb(struct intel_engine_cs *engine)
             ^~~~~~~~~~~
drivers/gpu/drm/i915/intel_lrc.c:994:13: error: static declaration of ‘process_csb’ follows non-static declaration
drivers/gpu/drm/i915/intel_lrc.c:946:2: note: previous implicit declaration of ‘process_csb’ was here
  process_csb(engine);
  ^~~~~~~~~~~
cc1: all warnings being treated as errors
scripts/Makefile.build:275: recipe for target 'drivers/gpu/drm/i915/intel_lrc.o' failed
make[4]: *** [drivers/gpu/drm/i915/intel_lrc.o] Error 1
scripts/Makefile.build:486: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2
scripts/Makefile.build:486: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:486: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1051: 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

  parent reply	other threads:[~2019-04-08 20:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 13:15 [PATCH] drm/i915/execlists: Always reset the context's RING registers Chris Wilson
2019-04-08 13:40 ` Chris Wilson
2019-04-08 15:38   ` Chris Wilson
2019-04-08 15:16 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/execlists: Always reset the context's RING registers (rev2) Patchwork
2019-04-08 15:36 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-04-08 15:45 ` [PATCH v3] drm/i915/execlists: Always reset the context's RING registers Chris Wilson
2019-04-08 18:51 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/execlists: Always reset the context's RING registers (rev3) Patchwork
2019-04-08 19:47 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-04-08 20:14 ` [PATCH v4] drm/i915/execlists: Always reset the context's RING registers Chris Wilson
2019-04-08 20:36 ` Chris Wilson
2019-04-08 20:38 ` Patchwork [this message]
2019-04-08 20:44 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/execlists: Always reset the context's RING registers (rev5) Patchwork
2019-04-08 21:12 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-09  2:10 ` ✓ 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=20190408203844.21094.32888@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --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