From: Patchwork <patchwork@emeril.freedesktop.org>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [v6,1/2] drm/i915/gtt: grab wakeref in gen6_alloc_va_range
Date: Wed, 29 May 2019 15:41:07 -0000 [thread overview]
Message-ID: <20190529154107.29224.99162@emeril.freedesktop.org> (raw)
In-Reply-To: <20190529123108.24422-1-matthew.auld@intel.com>
== Series Details ==
Series: series starting with [v6,1/2] drm/i915/gtt: grab wakeref in gen6_alloc_va_range
URL : https://patchwork.freedesktop.org/series/61323/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
eb05eacc4cba drm/i915/gtt: grab wakeref in gen6_alloc_va_range
514114e05ba7 drm/i915: add in-kernel blitter client
-:38: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#38:
new file mode 100644
-:403: CHECK:SPACING: spaces preferred around that '-' (ctx:VxV)
#403: FILE: drivers/gpu/drm/i915/gem/i915_gem_object_blt.c:22:
+ *cs++ = XY_COLOR_BLT_CMD | BLT_WRITE_RGBA | (7-2);
^
-:412: CHECK:SPACING: spaces preferred around that '-' (ctx:VxV)
#412: FILE: drivers/gpu/drm/i915/gem/i915_gem_object_blt.c:31:
+ *cs++ = XY_COLOR_BLT_CMD | BLT_WRITE_RGBA | (6-2);
^
-:544: WARNING:LINE_SPACING: Missing a blank line after declarations
#544: FILE: drivers/gpu/drm/i915/gem/selftests/i915_gem_client_blt.c:18:
+ struct rnd_state prng;
+ IGT_TIMEOUT(end);
-:677: WARNING:LINE_SPACING: Missing a blank line after declarations
#677: FILE: drivers/gpu/drm/i915/gem/selftests/i915_gem_object_blt.c:18:
+ struct rnd_state prng;
+ IGT_TIMEOUT(end);
-:778: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#778: FILE: drivers/gpu/drm/i915/gt/intel_gpu_commands.h:183:
+#define XY_COLOR_BLT_CMD (2<<29 | 0x50<<22)
^
-:778: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#778: FILE: drivers/gpu/drm/i915/gt/intel_gpu_commands.h:183:
+#define XY_COLOR_BLT_CMD (2<<29 | 0x50<<22)
^
total: 0 errors, 3 warnings, 4 checks, 726 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-29 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 12:31 [PATCH v6 1/2] drm/i915/gtt: grab wakeref in gen6_alloc_va_range Matthew Auld
2019-05-29 12:31 ` [PATCH v6 2/2] drm/i915: add in-kernel blitter client Matthew Auld
2019-05-29 15:41 ` Patchwork [this message]
2019-05-29 15:42 ` ✗ Fi.CI.SPARSE: warning for series starting with [v6,1/2] drm/i915/gtt: grab wakeref in gen6_alloc_va_range Patchwork
2019-05-29 16:26 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-05-31 8:25 ` 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=20190529154107.29224.99162@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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