From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for skl+ cursor DDB allocation fixes (rev2)
Date: Tue, 19 Mar 2019 16:41:42 -0000 [thread overview]
Message-ID: <20190319164142.6050.64897@emeril.freedesktop.org> (raw)
In-Reply-To: <20190312205844.6339-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: skl+ cursor DDB allocation fixes (rev2)
URL : https://patchwork.freedesktop.org/series/57901/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Accept alloc_size == blocks
Okay!
Commit: drm/i915: Don't pass plane state to skl_compute_plane_wm()
Okay!
Commit: drm/i915: Extract skl_compute_wm_params()
Okay!
Commit: drm/i915: Allocate enough DDB for the cursor
+drivers/gpu/drm/i915/intel_pm.c:3963:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/intel_pm.c:3963:16: warning: expression using sizeof(void)
-drivers/gpu/drm/i915/intel_pm.c:4458:25: warning: expression using sizeof(void)
-drivers/gpu/drm/i915/intel_pm.c:4458:25: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/intel_pm.c:4458:25: warning: too many warnings
-drivers/gpu/drm/i915/intel_pm.c:4943:30: warning: too many warnings
Commit: drm/i915: Make sure cursor has enough ddb for the selected wm level
Okay!
Commit: drm/i915: Keep plane watermarks enabled more aggressively
Okay!
Commit: drm/i915: Move some variables to tighter scope
-O:drivers/gpu/drm/i915/intel_pm.c:4454:25: warning: expression using sizeof(void)
-O:drivers/gpu/drm/i915/intel_pm.c:4454:25: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/intel_pm.c:4454:25: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/intel_pm.c:4454:25: warning: expression using sizeof(void)
Commit: drm/i915: Don't pass pipe_wm around so much
Okay!
Commit: drm/i915: Inline skl_build_pipe_wm() into its only caller
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-03-19 16:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 20:58 [PATCH 0/9] skl+ cursor DDB allocation fixes Ville Syrjala
2019-03-12 20:58 ` [PATCH 1/9] drm/i915: Accept alloc_size == blocks Ville Syrjala
2019-03-12 20:58 ` [PATCH 2/9] drm/i915: Don't pass plane state to skl_compute_plane_wm() Ville Syrjala
2019-03-12 20:58 ` [PATCH 3/9] drm/i915: Extract skl_compute_wm_params() Ville Syrjala
2019-03-12 20:58 ` [PATCH 4/9] drm/i915: Allocate enough DDB for the cursor Ville Syrjala
2019-03-19 10:51 ` Ville Syrjälä
2019-03-19 16:03 ` [PATCH v2 " Ville Syrjala
2019-03-12 20:58 ` [PATCH 5/9] drm/i915: Make sure cursor has enough ddb for the selected wm level Ville Syrjala
2019-03-12 20:58 ` [PATCH 6/9] drm/i915: Keep plane watermarks enabled more aggressively Ville Syrjala
2019-03-19 0:09 ` Matt Roper
2019-03-12 20:58 ` [PATCH 7/9] drm/i915: Move some variables to tighter scope Ville Syrjala
2019-03-19 0:10 ` Matt Roper
2019-03-20 15:27 ` Ville Syrjälä
2019-03-12 20:58 ` [PATCH 8/9] drm/i915: Don't pass pipe_wm around so much Ville Syrjala
2019-03-19 0:10 ` Matt Roper
2019-03-12 20:58 ` [PATCH 9/9] drm/i915: Inline skl_build_pipe_wm() into its only caller Ville Syrjala
2019-03-19 0:11 ` Matt Roper
2019-03-19 10:49 ` Ville Syrjälä
2019-03-13 15:34 ` ✗ Fi.CI.SPARSE: warning for skl+ cursor DDB allocation fixes Patchwork
2019-03-13 16:15 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-13 20:41 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-14 17:11 ` Ville Syrjälä
2019-03-19 16:41 ` Patchwork [this message]
2019-03-19 17:14 ` ✓ Fi.CI.BAT: success for skl+ cursor DDB allocation fixes (rev2) Patchwork
2019-03-20 2:41 ` ✓ 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=20190319164142.6050.64897@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox