From: Patchwork <patchwork@emeril.freedesktop.org>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for EHL port programming
Date: Fri, 21 Jun 2019 02:30:16 -0000 [thread overview]
Message-ID: <20190621023016.12829.52258@emeril.freedesktop.org> (raw)
In-Reply-To: <20190621020132.1164-1-matthew.d.roper@intel.com>
== Series Details ==
Series: EHL port programming
URL : https://patchwork.freedesktop.org/series/62492/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/icl: Drop port parameter to icl_get_combo_buf_trans()
Okay!
Commit: drm/i915/ehl: Add third combo PHY offset
Okay!
Commit: drm/i915/ehl: Don't program PHY_MISC on EHL PHY C
Okay!
Commit: drm/i915/gen11: Start distinguishing 'phy' from 'port'
+drivers/gpu/drm/i915/display/icl_dsi.c:370:58: int enum phy
+drivers/gpu/drm/i915/display/icl_dsi.c:370:58: int enum port versus
+drivers/gpu/drm/i915/display/icl_dsi.c:370:58: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_combo_phy.c:199:46: int enum phy versus
+drivers/gpu/drm/i915/display/intel_combo_phy.c:199:46: int enum port
+drivers/gpu/drm/i915/display/intel_combo_phy.c:199:46: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_combo_phy.c:202:55: int enum phy versus
+drivers/gpu/drm/i915/display/intel_combo_phy.c:202:55: int enum port
+drivers/gpu/drm/i915/display/intel_combo_phy.c:202:55: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_combo_phy.c:205:48: int enum phy versus
+drivers/gpu/drm/i915/display/intel_combo_phy.c:205:48: int enum port
+drivers/gpu/drm/i915/display/intel_combo_phy.c:205:48: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_combo_phy.c:208:40: int enum phy versus
+drivers/gpu/drm/i915/display/intel_combo_phy.c:208:40: int enum port
+drivers/gpu/drm/i915/display/intel_combo_phy.c:208:40: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_combo_phy.c:327:54: int enum phy versus
+drivers/gpu/drm/i915/display/intel_combo_phy.c:327:54: int enum port
+drivers/gpu/drm/i915/display/intel_combo_phy.c:327:54: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum phy versus
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum phy versus
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum phy versus
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum phy versus
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum phy versus
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum port
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum port
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum port
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum port
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: int enum port
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_ddi.c:2740:67: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_ddi.c:2846:68: int enum phy
+drivers/gpu/drm/i915/display/intel_ddi.c:2846:68: int enum port versus
+drivers/gpu/drm/i915/display/intel_ddi.c:2846:68: warning: mixing different enum types
+drivers/gpu/drm/i915/display/intel_ddi.c:2860:60: int enum phy
+drivers/gpu/drm/i915/display/intel_ddi.c:2860:60: int enum port versus
+drivers/gpu/drm/i915/display/intel_ddi.c:2860:60: warning: mixing different enum types
Commit: drm/i915/ehl: Enable DDI-D
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-21 2:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 2:01 [PATCH 0/5] EHL port programming Matt Roper
2019-06-21 2:01 ` [PATCH 1/5] drm/i915/icl: Drop port parameter to icl_get_combo_buf_trans() Matt Roper
2019-06-21 22:23 ` Clinton Taylor
2019-06-21 2:01 ` [PATCH 2/5] drm/i915/ehl: Add third combo PHY offset Matt Roper
2019-06-21 20:19 ` Souza, Jose
2019-06-21 2:01 ` [PATCH 3/5] drm/i915/ehl: Don't program PHY_MISC on EHL PHY C Matt Roper
2019-06-21 20:34 ` Souza, Jose
2019-06-21 2:01 ` [PATCH 4/5] drm/i915/gen11: Start distinguishing 'phy' from 'port' Matt Roper
2019-06-21 14:08 ` Matt Roper
2019-06-22 0:24 ` Souza, Jose
2019-06-25 12:46 ` Ville Syrjälä
2019-06-25 20:54 ` Matt Roper
2019-06-21 2:01 ` [PATCH 5/5] drm/i915/ehl: Enable DDI-D Matt Roper
2019-06-21 20:52 ` Souza, Jose
2019-06-25 22:19 ` Matt Roper
2019-06-26 21:11 ` Souza, Jose
2019-06-21 2:27 ` ✗ Fi.CI.CHECKPATCH: warning for EHL port programming Patchwork
2019-06-21 2:30 ` Patchwork [this message]
2019-06-21 3:04 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-21 9:09 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-21 14:36 ` ✗ Fi.CI.CHECKPATCH: warning for EHL port programming (rev2) Patchwork
2019-06-21 14:59 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-21 21:21 ` ✗ Fi.CI.IGT: failure " 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=20190621023016.12829.52258@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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.