From: Patchwork <patchwork@emeril.freedesktop.org>
To: Navare@emeril.freedesktop.org, Manasi D <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for Link Training failure handling during modeset (rev4)
Date: Sat, 19 Nov 2016 04:01:29 -0000 [thread overview]
Message-ID: <20161119040129.10606.48104@emeril.freedesktop.org> (raw)
In-Reply-To: <1479453200-27705-1-git-send-email-manasi.d.navare@intel.com>
== Series Details ==
Series: Link Training failure handling during modeset (rev4)
URL : https://patchwork.freedesktop.org/series/15537/
State : failure
== Summary ==
(_timer)->data = (_data); \
^
./include/linux/workqueue.h:247:2: note: in expansion of macro ‘__INIT_DELAYED_WORK’
__INIT_DELAYED_WORK(_work, _func, 0)
^
drivers/gpu/drm/i915/intel_dp.c:5745:2: note: in expansion of macro ‘INIT_DELAYED_WORK’
INIT_DELAYED_WORK(&intel_dp->panel_vdd_work,
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘intel_dp_mst_suspend’:
drivers/gpu/drm/i915/intel_dp.c:5899:45: error: ‘struct intel_dp’ has no member named ‘can_mst’
if (!intel_dig_port || !intel_dig_port->dp.can_mst)
^
drivers/gpu/drm/i915/intel_dp.c:5902:25: error: ‘struct intel_dp’ has no member named ‘is_mst’
if (intel_dig_port->dp.is_mst)
^
drivers/gpu/drm/i915/intel_dp.c:5903:55: error: ‘struct intel_dp’ has no member named ‘mst_mgr’
drm_dp_mst_topology_mgr_suspend(&intel_dig_port->dp.mst_mgr);
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘intel_dp_mst_resume’:
drivers/gpu/drm/i915/intel_dp.c:5916:45: error: ‘struct intel_dp’ has no member named ‘can_mst’
if (!intel_dig_port || !intel_dig_port->dp.can_mst)
^
drivers/gpu/drm/i915/intel_dp.c:5919:59: error: ‘struct intel_dp’ has no member named ‘mst_mgr’
ret = drm_dp_mst_topology_mgr_resume(&intel_dig_port->dp.mst_mgr);
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘__intel_dp_read_desc’:
drivers/gpu/drm/i915/intel_dp.c:1501:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘intel_dp_rate_select’:
drivers/gpu/drm/i915/intel_dp.c:1551:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
scripts/Makefile.build:290: recipe for target 'drivers/gpu/drm/i915/gvt/scheduler.o' failed
make[4]: *** [drivers/gpu/drm/i915/gvt/scheduler.o] Error 1
drivers/gpu/drm/i915/intel_dp.c: In function ‘vlv_power_sequencer_pipe’:
drivers/gpu/drm/i915/intel_dp.c:568:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘intel_dp_get_link_status’:
drivers/gpu/drm/i915/intel_dp.c:3013:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘intel_dp_read_dpcd’:
drivers/gpu/drm/i915/intel_dp.c:3545:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘intel_dp_connector_register’:
drivers/gpu/drm/i915/intel_dp.c:4695:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
drivers/gpu/drm/i915/intel_dp.c: In function ‘intel_dp_get_edid’:
drivers/gpu/drm/i915/intel_dp.c:4361:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
cc1: all warnings being treated as errors
scripts/Makefile.build:290: recipe for target 'drivers/gpu/drm/i915/gvt/gtt.o' failed
make[4]: *** [drivers/gpu/drm/i915/gvt/gtt.o] Error 1
scripts/Makefile.build:290: recipe for target 'drivers/gpu/drm/i915/intel_dp.o' failed
make[4]: *** [drivers/gpu/drm/i915/intel_dp.o] Error 1
scripts/Makefile.build:290: recipe for target 'drivers/gpu/drm/i915/i915_trace_points.o' failed
make[4]: *** [drivers/gpu/drm/i915/i915_trace_points.o] Error 1
scripts/Makefile.build:290: recipe for target 'drivers/gpu/drm/i915/gvt/handlers.o' failed
make[4]: *** [drivers/gpu/drm/i915/gvt/handlers.o] Error 1
CC arch/x86/kernel/cpu/capflags.o
LD arch/x86/kernel/cpu/built-in.o
scripts/Makefile.build:475: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2
scripts/Makefile.build:475: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:475: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
LD arch/x86/kernel/built-in.o
LD drivers/pci/built-in.o
LD arch/x86/built-in.o
LD fs/btrfs/btrfs.o
AR lib/lib.a
EXPORTS lib/lib-ksyms.o
LD lib/built-in.o
LD fs/btrfs/built-in.o
LD drivers/md/md-mod.o
LD drivers/md/built-in.o
LD drivers/usb/host/xhci-hcd.o
LD drivers/tty/vt/built-in.o
LD drivers/tty/built-in.o
LD net/ipv4/built-in.o
LD drivers/usb/host/built-in.o
LD drivers/usb/built-in.o
LD fs/ext4/ext4.o
LD fs/ext4/built-in.o
LD fs/built-in.o
LD [M] drivers/net/ethernet/intel/igb/igb.o
LD [M] drivers/net/ethernet/intel/e1000e/e1000e.o
LD net/core/built-in.o
LD net/built-in.o
LD drivers/net/ethernet/built-in.o
LD drivers/net/built-in.o
Makefile:985: 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:[~2016-11-19 4:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 7:13 [PATCH 0/5] Link Training failure handling during modeset Manasi Navare
2016-11-18 7:13 ` [PATCH 1/5] drm: Add a new connector property for link status Manasi Navare
2016-11-19 2:50 ` [PATCH v5 " Manasi Navare
2016-11-21 9:33 ` Daniel Vetter
2016-11-18 7:13 ` [PATCH 2/5] drm: Set DRM connector link status property Manasi Navare
2016-11-19 2:50 ` [PATCH v3 " Manasi Navare
2016-11-18 7:13 ` [PATCH 3/5] drm/i915: Update CRTC state if connector link status property changed Manasi Navare
2016-11-18 13:50 ` Maarten Lankhorst
2016-11-18 14:11 ` Ville Syrjälä
2016-11-18 14:18 ` Maarten Lankhorst
2016-11-18 15:28 ` Ville Syrjälä
2016-11-18 15:35 ` [Intel-gfx] " Daniel Vetter
2016-11-18 16:21 ` Ville Syrjälä
2016-11-18 17:44 ` [Intel-gfx] " Manasi Navare
2016-11-21 9:38 ` Daniel Vetter
2016-11-21 9:42 ` Chris Wilson
2016-11-21 10:10 ` [Intel-gfx] " Daniel Vetter
2016-11-21 15:48 ` Daniel Vetter
2016-11-21 19:00 ` Manasi Navare
2016-11-21 20:46 ` Chris Wilson
2016-11-21 21:07 ` [Intel-gfx] " Manasi Navare
2016-11-23 1:15 ` Manasi Navare
2016-11-23 7:44 ` Daniel Vetter
2016-11-18 18:13 ` [Intel-gfx] " Manasi Navare
2016-11-18 15:23 ` Manasi Navare
2016-11-18 7:13 ` [PATCH 4/5] drm/i915: Find fallback link rate/lane count Manasi Navare
2016-11-18 7:29 ` Manasi Navare
2016-11-18 13:22 ` Jani Nikula
2016-11-18 15:39 ` Manasi Navare
2016-11-19 2:09 ` Manasi Navare
2016-11-19 2:50 ` [PATCH v6 4/56 4/56 4/56 4/56 4/56 " Manasi Navare
2016-11-18 7:13 ` [PATCH 5/5] drm/i915: Implement Link Rate fallback on Link training failure Manasi Navare
2016-11-18 7:29 ` Manasi Navare
2016-11-18 13:31 ` Jani Nikula
2016-11-18 15:29 ` Manasi Navare
2016-11-19 2:50 ` [PATCH v8 " Manasi Navare
2016-11-18 8:31 ` ✗ Fi.CI.BAT: failure for Link Training failure handling during modeset (rev3) Patchwork
2016-11-19 4:01 ` 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=20161119040129.10606.48104@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=Navare@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).