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 series starting with [1/9] drm/i915/perf: store the associated engine of a stream
Date: Thu, 10 Oct 2019 00:07:47 -0000 [thread overview]
Message-ID: <20191010000747.31952.66768@emeril.freedesktop.org> (raw)
In-Reply-To: <20191009211947.6815-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/9] drm/i915/perf: store the associated engine of a stream
URL : https://patchwork.freedesktop.org/series/67804/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
bf2b0e099619 drm/i915/perf: store the associated engine of a stream
4726bb22ec6f drm/i915/perf: introduce a versioning of the i915-perf uapi
635bb86b7638 drm/i915/perf: allow for CS OA configs to be created lazily
0c88bb75cd92 drm/i915: add support for perf configuration queries
37d537db43fb drm/i915/perf: implement active wait for noa configurations
-:45: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#45: FILE: drivers/gpu/drm/i915/gt/intel_gpu_commands.h:228:
+#define PIPE_CONTROL_WRITE_TIMESTAMP (3<<14)
^
-:179: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#179: FILE: drivers/gpu/drm/i915/i915_perf.c:1567:
+ DIV64_U64_ROUND_UP(
-:213: CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#213: FILE: drivers/gpu/drm/i915/i915_perf.c:1601:
+ batch = cs = i915_gem_object_pin_map(bo, I915_MAP_WB);
-:221: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#221: FILE: drivers/gpu/drm/i915/i915_perf.c:1609:
+ cs = save_restore_register(
-:224: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#224: FILE: drivers/gpu/drm/i915/i915_perf.c:1612:
+ cs = save_restore_register(
-:326: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#326: FILE: drivers/gpu/drm/i915/i915_perf.c:1714:
+ cs = save_restore_register(
-:329: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#329: FILE: drivers/gpu/drm/i915/i915_perf.c:1717:
+ cs = save_restore_register(
-:446: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#446:
new file mode 100644
-:451: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#451: FILE: drivers/gpu/drm/i915/selftests/i915_perf.c:1:
+/*
-:452: WARNING:SPDX_LICENSE_TAG: Misplaced SPDX-License-Identifier tag - use line 1 instead
#452: FILE: drivers/gpu/drm/i915/selftests/i915_perf.c:2:
+ * SPDX-License-Identifier: MIT
total: 0 errors, 3 warnings, 7 checks, 590 lines checked
c8c01bdf5c02 drm/i915/perf: execute OA configuration from command stream
047ce24b0f91 drm/i915/perf: Allow dynamic reconfiguration of the OA stream
5d1246ef0b93 drm/i915/perf: allow holding preemption on filtered ctx
e3f2dcd26998 drm/i915/execlists: Prevent merging requests with conflicting flags
-:14: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#14:
References: 2a98f4e65bba ("drm/i915: add infrastructure to hold off preemption on a request")
-:14: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 2a98f4e65bba ("drm/i915: add infrastructure to hold off preemption on a request")'
#14:
References: 2a98f4e65bba ("drm/i915: add infrastructure to hold off preemption on a request")
total: 1 errors, 1 warnings, 0 checks, 9 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-10-10 0:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 21:19 [PATCH 1/9] drm/i915/perf: store the associated engine of a stream Chris Wilson
2019-10-09 21:19 ` [PATCH 2/9] drm/i915/perf: introduce a versioning of the i915-perf uapi Chris Wilson
2019-10-09 21:19 ` [PATCH 3/9] drm/i915/perf: allow for CS OA configs to be created lazily Chris Wilson
2019-10-09 21:19 ` [PATCH 4/9] drm/i915: add support for perf configuration queries Chris Wilson
2019-10-09 21:19 ` [PATCH 5/9] drm/i915/perf: implement active wait for noa configurations Chris Wilson
2019-10-09 21:19 ` [PATCH 6/9] drm/i915/perf: execute OA configuration from command stream Chris Wilson
2019-10-09 21:19 ` [PATCH 7/9] drm/i915/perf: Allow dynamic reconfiguration of the OA stream Chris Wilson
2019-10-10 15:22 ` Lionel Landwerlin
2019-10-10 15:44 ` Chris Wilson
[not found] ` <8e58da7d-9ec9-4225-3e24-d7e6665d8a17@intel.com>
2019-10-10 19:50 ` Chris Wilson
2019-10-10 21:08 ` Lionel Landwerlin
2019-10-09 21:19 ` [PATCH 8/9] drm/i915/perf: allow holding preemption on filtered ctx Chris Wilson
2019-10-09 21:19 ` [PATCH 9/9] drm/i915/execlists: Prevent merging requests with conflicting flags Chris Wilson
2019-10-10 16:09 ` Lionel Landwerlin
2019-10-10 0:07 ` Patchwork [this message]
2019-10-10 0:34 ` ✓ Fi.CI.BAT: success for series starting with [1/9] drm/i915/perf: store the associated engine of a stream Patchwork
2019-10-10 10:25 ` ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-10-08 21:40 Reconfigurable OA queries Chris Wilson
2019-10-08 22:38 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915/perf: store the associated engine of a stream 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=20191010000747.31952.66768@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