public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lyude Paul <lyude@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for DP MST Refactors + debugging tools + suspend/resume reprobing
Date: Tue, 22 Oct 2019 03:02:01 -0000	[thread overview]
Message-ID: <20191022030201.9306.54671@emeril.freedesktop.org> (raw)
In-Reply-To: <20191022023641.8026-1-lyude@redhat.com>

== Series Details ==

Series: DP MST Refactors + debugging tools + suspend/resume reprobing
URL   : https://patchwork.freedesktop.org/series/68359/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/dp_mst: Destroy MSTBs asynchronously
Okay!

Commit: drm/dp_mst: Remove PDT teardown in drm_dp_destroy_port() and refactor
Okay!

Commit: drm/dp_mst: Refactor pdt setup/teardown, add more locking
Okay!

Commit: drm/dp_mst: Handle UP requests asynchronously
Okay!

Commit: drm/dp_mst: Add probe_lock
+                     ^~~
+drivers/gpu/drm/drm_dp_mst_topology.c:2178:21: warning: unused variable ‘dev’ [-Wunused-variable]
+drivers/gpu/drm/drm_dp_mst_topology.c: In function ‘drm_dp_mst_link_probe_work’:
+  struct drm_device *dev = mgr->dev;

Commit: drm/dp_mst: Protect drm_dp_mst_port members with locking
-                     ^~~
-drivers/gpu/drm/drm_dp_mst_topology.c:2244:21: warning: unused variable ‘dev’ [-Wunused-variable]
-drivers/gpu/drm/drm_dp_mst_topology.c: In function ‘drm_dp_mst_link_probe_work’:
-  struct drm_device *dev = mgr->dev;

Commit: drm/dp_mst: Don't forget to update port->input in drm_dp_mst_handle_conn_stat()
Okay!

Commit: drm/dp_mst: Lessen indenting in drm_dp_mst_topology_mgr_resume()
Okay!

Commit: drm/nouveau: Don't grab runtime PM refs for HPD IRQs
Okay!

Commit: drm/nouveau: Resume hotplug interrupts earlier
Okay!

Commit: drm/amdgpu: Iterate through DRM connectors correctly
-drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1919:24: warning: symbol 'dm_atomic_get_new_state' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1937:24: warning: symbol 'dm_atomic_get_old_state' was not declared. Should it be static?
-drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4444:6: warning: symbol 'dm_drm_plane_destroy_state' was not declared. Should it be static?
+drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1922:24: warning: symbol 'dm_atomic_get_new_state' was not declared. Should it be static?
+drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1940:24: warning: symbol 'dm_atomic_get_old_state' was not declared. Should it be static?
+drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4447:6: warning: symbol 'dm_drm_plane_destroy_state' was not declared. Should it be static?

Commit: drm/amdgpu/dm: Resume short HPD IRQs before resuming MST topology
Okay!

Commit: drm/dp_mst: Add basic topology reprobing when resuming
Okay!

Commit: drm/dp_mst: Add topology ref history tracking for debugging
Okay!

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-10-22  3:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  2:35 [PATCH v5 00/14] DP MST Refactors + debugging tools + suspend/resume reprobing Lyude Paul
2019-10-22  2:35 ` [PATCH v5 01/14] drm/dp_mst: Destroy MSTBs asynchronously Lyude Paul
2019-10-22  2:35 ` [PATCH v5 02/14] drm/dp_mst: Remove PDT teardown in drm_dp_destroy_port() and refactor Lyude Paul
2019-10-22  2:35 ` [PATCH v5 03/14] drm/dp_mst: Refactor pdt setup/teardown, add more locking Lyude Paul
2019-10-22  2:35 ` [PATCH v5 04/14] drm/dp_mst: Handle UP requests asynchronously Lyude Paul
2019-10-22  2:36 ` [PATCH v5 05/14] drm/dp_mst: Add probe_lock Lyude Paul
2019-10-22 16:06   ` Sean Paul
2019-10-22  2:36 ` [PATCH v5 06/14] drm/dp_mst: Protect drm_dp_mst_port members with locking Lyude Paul
2019-10-22 20:08   ` Sean Paul
2019-10-22  2:36 ` [PATCH v5 07/14] drm/dp_mst: Don't forget to update port->input in drm_dp_mst_handle_conn_stat() Lyude Paul
2019-10-22 20:14   ` Sean Paul
2019-10-22  2:36 ` [PATCH v5 08/14] drm/dp_mst: Lessen indenting in drm_dp_mst_topology_mgr_resume() Lyude Paul
2019-10-22  2:36 ` [PATCH v5 09/14] drm/nouveau: Don't grab runtime PM refs for HPD IRQs Lyude Paul
2019-10-22  2:36 ` [PATCH v5 10/14] drm/nouveau: Resume hotplug interrupts earlier Lyude Paul
2019-10-22  2:36 ` [PATCH v5 11/14] drm/amdgpu: Iterate through DRM connectors correctly Lyude Paul
2019-10-22  2:36 ` [PATCH v5 12/14] drm/amdgpu/dm: Resume short HPD IRQs before resuming MST topology Lyude Paul
2019-10-22  2:36 ` [PATCH v5 13/14] drm/dp_mst: Add basic topology reprobing when resuming Lyude Paul
2019-10-22  2:36 ` [PATCH v5 14/14] drm/dp_mst: Add topology ref history tracking for debugging Lyude Paul
2019-10-22  2:54 ` ✗ Fi.CI.CHECKPATCH: warning for DP MST Refactors + debugging tools + suspend/resume reprobing Patchwork
2019-10-22  3:02 ` Patchwork [this message]
2019-10-22  3:19 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-22 12:46 ` ✓ 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=20191022030201.9306.54671@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lyude@redhat.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