public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev19)
Date: Fri, 25 Jan 2019 15:32:42 -0000	[thread overview]
Message-ID: <20190125153242.3644.88931@emeril.freedesktop.org> (raw)
In-Reply-To: <20190125152441.5080-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: Per context dynamic (sub)slice power-gating (rev19)
URL   : https://patchwork.freedesktop.org/series/48194/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
b46b66196670 drm/i915: Record the sseu configuration per-context & engine
56a1aaefc8e7 drm/i915/perf: lock powergating configuration to default when active
1915b804bb44 drm/i915: Add timeline barrier support
bcb0cea5b5b1 drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only)
-:528: CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around 'user->min_eus_per_subslice !=
 		     device->max_eus_per_subslice'
#528: FILE: drivers/gpu/drm/i915/i915_gem_context.c:1175:
+		if ((user->min_eus_per_subslice !=
+		     device->max_eus_per_subslice) ||
+		    (user->max_eus_per_subslice !=
+		     device->max_eus_per_subslice))

-:528: CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around 'user->max_eus_per_subslice !=
 		     device->max_eus_per_subslice'
#528: FILE: drivers/gpu/drm/i915/i915_gem_context.c:1175:
+		if ((user->min_eus_per_subslice !=
+		     device->max_eus_per_subslice) ||
+		    (user->max_eus_per_subslice !=
+		     device->max_eus_per_subslice))

total: 0 errors, 0 warnings, 2 checks, 499 lines checked
e930fd0346d9 drm/i915/selftests: Context SSEU reconfiguration tests

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

  parent reply	other threads:[~2019-01-25 15:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 15:24 [PATCH 0/5] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2019-01-25 15:24 ` [PATCH 1/5] drm/i915: Record the sseu configuration per-context & engine Tvrtko Ursulin
2019-01-25 15:24 ` [PATCH 2/5] drm/i915/perf: lock powergating configuration to default when active Tvrtko Ursulin
2019-01-25 15:24 ` [PATCH 3/5] drm/i915: Add timeline barrier support Tvrtko Ursulin
2019-01-25 15:37   ` Chris Wilson
2019-01-25 17:06   ` [PATCH v4 " Tvrtko Ursulin
2019-01-25 15:24 ` [PATCH 4/5] drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only) Tvrtko Ursulin
2019-01-26 10:57   ` Chris Wilson
2019-01-25 15:24 ` [PATCH 5/5] drm/i915/selftests: Context SSEU reconfiguration tests Tvrtko Ursulin
2019-01-25 15:32 ` Patchwork [this message]
2019-01-25 15:35 ` ✗ Fi.CI.SPARSE: warning for Per context dynamic (sub)slice power-gating (rev19) Patchwork
2019-01-25 16:01 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-01-25 17:19 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev20) Patchwork
2019-01-25 17:22 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-25 17:37 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-25 20:23 ` ✗ 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=20190125153242.3644.88931@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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