From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: Engine discovery query (rev9)
Date: Thu, 02 May 2019 05:54:35 -0000 [thread overview]
Message-ID: <20190502055435.14432.27315@emeril.freedesktop.org> (raw)
In-Reply-To: <20190502053853.22191-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: drm/i915: Engine discovery query (rev9)
URL : https://patchwork.freedesktop.org/series/39958/
State : failure
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
AR drivers/gpu/drm/i915/built-in.a
CC [M] drivers/gpu/drm/i915/header_test_i915_active_types.o
CC [M] drivers/gpu/drm/i915/header_test_i915_drv.o
CC [M] drivers/gpu/drm/i915/header_test_i915_gem_context_types.o
CC [M] drivers/gpu/drm/i915/header_test_i915_gem_pm.o
CC [M] drivers/gpu/drm/i915/header_test_i915_irq.o
CC [M] drivers/gpu/drm/i915/header_test_i915_params.o
CC [M] drivers/gpu/drm/i915/header_test_i915_priolist_types.o
CC [M] drivers/gpu/drm/i915/header_test_i915_reg.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.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_bios.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_combo_phy.o
CC [M] drivers/gpu/drm/i915/header_test_intel_connector.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_dp_aux_backlight.o
CC [M] drivers/gpu/drm/i915/header_test_intel_dp_link_training.o
CC [M] drivers/gpu/drm/i915/header_test_intel_dp_mst.o
CC [M] drivers/gpu/drm/i915/header_test_intel_dpll_mgr.o
CC [M] drivers/gpu/drm/i915/header_test_intel_drv.o
CC [M] drivers/gpu/drm/i915/header_test_intel_dsi.o
CC [M] drivers/gpu/drm/i915/header_test_intel_dsi_dcs_backlight.o
CC [M] drivers/gpu/drm/i915/header_test_intel_dvo.o
CC [M] drivers/gpu/drm/i915/header_test_intel_dvo_dev.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_fifo_underrun.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_hotplug.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_overlay.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_quirks.o
CC [M] drivers/gpu/drm/i915/header_test_intel_sdvo.o
CC [M] drivers/gpu/drm/i915/header_test_intel_sideband.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_uncore.o
CC [M] drivers/gpu/drm/i915/header_test_intel_vdsc.o
CC [M] drivers/gpu/drm/i915/header_test_intel_wakeref.o
CC [M] drivers/gpu/drm/i915/gt/intel_engine_cs.o
drivers/gpu/drm/i915/gt/intel_engine_cs.c: In function ‘intel_engines_init_mmio’:
drivers/gpu/drm/i915/gt/intel_engine_cs.c:456:34: error: ‘dev_priv’ undeclared (first use in this function); did you mean ‘dev_crit’?
intel_setup_engine_capabilities(dev_priv);
^~~~~~~~
dev_crit
drivers/gpu/drm/i915/gt/intel_engine_cs.c:456:34: note: each undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:275: recipe for target 'drivers/gpu/drm/i915/gt/intel_engine_cs.o' failed
make[4]: *** [drivers/gpu/drm/i915/gt/intel_engine_cs.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
prev parent reply other threads:[~2019-05-02 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 5:38 [CI v11] drm/i915: Engine discovery query Tvrtko Ursulin
2019-05-02 5:54 ` Patchwork [this message]
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=20190502055435.14432.27315@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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