From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ville Syrjala" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Plumb crtc state to link training code
Date: Wed, 06 May 2020 11:29:51 -0000 [thread overview]
Message-ID: <158876459115.11898.11217160018092564313@emeril.freedesktop.org> (raw)
In-Reply-To: <20200506112328.16562-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: drm/i915: Plumb crtc state to link training code
URL : https://patchwork.freedesktop.org/series/76993/
State : failure
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
HDRTEST drivers/gpu/drm/i915/display/intel_dp_link_training.h
In file included from <command-line>:0:0:
./drivers/gpu/drm/i915/display/intel_dp_link_training.h:14:24: error: ‘struct intel_crtc_state’ declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
const struct intel_crtc_state *crtc_state,
^~~~~~~~~~~~~~~~
./drivers/gpu/drm/i915/display/intel_dp_link_training.h:17:24: error: ‘struct intel_crtc_state’ declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
const struct intel_crtc_state *crtc_state);
^~~~~~~~~~~~~~~~
./drivers/gpu/drm/i915/display/intel_dp_link_training.h:19:23: error: ‘struct intel_crtc_state’ declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
const struct intel_crtc_state *crtc_state);
^~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
drivers/gpu/drm/i915/Makefile:299: recipe for target 'drivers/gpu/drm/i915/display/intel_dp_link_training.hdrtest' failed
make[4]: *** [drivers/gpu/drm/i915/display/intel_dp_link_training.hdrtest] Error 1
scripts/Makefile.build:488: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2
scripts/Makefile.build:488: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:488: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1722: 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-05-06 11:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 11:23 [Intel-gfx] [PATCH 0/9] drm/i915: Plumb crtc state to link training code Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 1/9] drm/i915: Fix cpt/ppt max pre-emphasis Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 2/9] drm/i915: Fix ibx max vswing/preemph Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 3/9] drm/i915: Fix ivb cpu edp vswing Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 4/9] drm/i915: Add {preemph, voltage}_max() vfuncs Ville Syrjala
2020-05-07 7:09 ` Ville Syrjälä
2020-05-06 11:23 ` [Intel-gfx] [PATCH 5/9] drm/i915: Reverse preemph vs. voltage swing preference Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 6/9] drm/i915: Fix DP_TRAIN_MAX_{PRE_EMPHASIS, SWING}_REACHED handling Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 7/9] drm/i915: Replace some hand rolled max()s Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 8/9] drm/i915: Plumb crtc_state to link training Ville Syrjala
2020-05-06 12:05 ` [Intel-gfx] [PATCH v2 " Ville Syrjala
2020-05-06 11:23 ` [Intel-gfx] [PATCH 9/9] drm/i915: Eliminate intel_dp.regs.dp_tp_{ctl, status} Ville Syrjala
2020-05-06 11:29 ` Patchwork [this message]
2020-05-06 12:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Plumb crtc state to link training code (rev2) Patchwork
2020-05-06 13:48 ` [Intel-gfx] ✓ 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=158876459115.11898.11217160018092564313@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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.